91–100 of 336 posts
Perhaps it's due to me being in the PostgreSQL camp, but what happened to MariaDB? I was convinced that's where MySQL developers went and that's where development proceeded, while MySQL was just half dead, because Oracle did not care about it.
It's interesting to see FB migrating so much over to Oracle. 2 weeks ago was FB use of GraalVM (from Oracle). And now this. https://news.ycombinator.com/item?id=27782475
Earlier quoted context omitted.
Ah this is interesting. Do you have any references on their migration to Spanner?
gresrun works at YouTube, if by reference you mean citation then his comment is it.
Earlier quoted context omitted.
Youtube also use MySQL.
YouTube used to use a MySQL-based system called Vitess[0]. It no longer uses it and has migrated to Spanner. [0]: https://vitess.io/
> How Google uses Vitess
> Vitess was serving all YouTube database traffic from 2011 to 2019.
Earlier quoted context omitted.
I always see people asking about this. But why? Are you making schema changes that frequently?
It's my opinion that schema changes should be cheap, fast and unexciting. Unfortunately, in my experience once you are operating at scale they are expensive, slow and fraught with peril. The result is that engineering teams often chose to build poorly designed schemas and take on technical debt rather than make a schema change to a core table. This is a terrible anti-pattern! I'm massively in favour of anything that…
begin tran
..refactor data, drop/create tables..
..create backwards-compatible views..
commit
Perhaps it's due to me being in the PostgreSQL camp, but what happened to MariaDB? I was convinced that's where MySQL developers went and that's where development proceeded, while MySQL was just half dead, because Oracle did not care about it.
That was the expectation but the Oracle camp surprised everyone by actually giving it some attention, and meanwhile MariaDB's promise of being a "100% compatible drop-in replacement" came with more and more caveats with each release (as is to be entirely expected with any fork). When you consider the network effect of all the stacks already heavily invested in MySQL, all Oracle really needed to do was put in a modicu…
I absolutely adore Postgres's tweaks to the SQL language, that dialect is amazing and has served us extremely well. And, since we passed pg10 a while back, the performance tuning you can do on it is pretty amazing.
Seems like good, old-fashioned engineering work to me. No breathless evangelism or careerist claptrap in sight.
My impression too. Very meticulous work, just the facts.
Earlier quoted context omitted.
Like everyone else?
I didn't downvote you, but you were downvoted for this. So maybe I'll explain further, instead, to stir conversation. As you deal with more and more rows, it becomes imperative that all of your where clauses hit indexes/indices, but even beyond that, with large enough row sizes, it's not enough to provide fast responses. I suspect they deal with this in the form of some sort of caching outside of MySQL, but I haven't…
Similar story at nearly every large tech company using MySQL, aside from some more recent ones that go for the painful "shove everything in a huge singular AWS Aurora instance" approach :)
Earlier quoted context omitted.
Oracle has a very complete and much cheaper cloud solution relative to AWS. I've begun migrating my own projects over to their cloud. The savings on egress costs alone pays dividends.
Totally off topic, but I found it funny that in the offical oracle cloud intro video the robot arm in the background misses the box, right as the narrator mentions the advantages of automation at 1:10: https://www.youtube.com/watch?v=f_BDfMdGn3M&t=61s
Earlier quoted context omitted.
And yet MySQL is very much alive..? Java has fully opensource implementations too, and has had innovations like GraalVM and Jakarta EE. I think I'm too young to hate Oracle with a burning passion. I would be very scared of their sales/corporate team, but I mean, even having large contracts with Google or Amazon is difficult to say the least.
MySQL is alive for companies already using MySQL, but would well informed companies be choosing it today? I'm not so sure. I think you either want it to have more functionality and you choose Postgres, you want a particular performance profile and you pick MariaDB, or you want the enterprise support and you pick Oracle's database. Why you would pick Oracle-supported MySQL today I'm not sure.