Tech debt is a great topic for learning. But it is hard to discuss in public because it becomes marketing fodder for the competition.
MySQL has tech debt just like all other mature DBMS, and it is a great product despite that.
Conversation
Replying to
As a Postgres person, I would much rather hear about MySQL's notable strengths. Weaknesses *can* be interesting when they hint at an interesting underlying trade-off, but not otherwise. The fact that the MySQL optimizer is subpar is well known, and of no interest to me.
Well said. Better learn strength and weakness from people making it work the best they can rather than people leaving by frustration, which is probably more context related than tech
3
Thanks for saying this the way you did.
I had some not-positive reactions to that blog but couldn’t figure out how to articulate them.
You put things in perspective here.
1
1
I didn't mind the article and the content was truthy. But I am not a fan of turning it into clickbait (on reddit, article in The Register).
1
Yeah, the entire piece has an odd vibe to it. Just seems weird to talk down that way on the thing you've been working on for the last five years. Also his picture of Postgres is a bit too rosy (to be clear, I love PG), there's things MySQL does better actually.
1
3
You’re unable to view this Tweet because this account owner limits who can view their Tweets. Learn more
Show replies
Replying to
For me: OLTP, InnoDB, replication, community and the storage engine API.
1
2
Replying to
I was the primary author of on ON CONFLICT DO UPDATE in Postgres. That design owes plenty to MySQL. Asserting that you have nothing to learn from so-called "out-group" always seems like self-indulgence to me.
4