Impressions (Leaving MySQL)
# Random TalkThis morning I came across this article Leaving MySQL. If there’s one key takeaway from the article, it’s what the author writes:
MySQL is a pretty poor database, and you should strongly consider using Postgres instead.
The footnote even points out that using MariaDB isn’t any better.
I first learned about PostgreSQL through Ruby on Rails. At that time, I encountered some issues while setting up MySQL, so I used PostgreSQL as the database. Ever since then, whenever I’m working with databases, PostgreSQL has been my go-to choice.
Later on, I discovered some of the more appealing features of PostgreSQL, such as support for JSON types (if I recall correctly, MySQL didn’t support this at the time) and its rich INDEX configurations1. At that time, I even tried out PostGIS for practicing geographical applications. In short, my experience with PostgreSQL has always been excellent, and I encourage you to continue choosing PostgreSQL.
Footnotes
Related Posts
- Defaults and TasteAn essay extending Wiwi’s “Default” — discussing the unwritten rules of Fukuoka escalators, how AI content takes over SEO rankings, and Voltaire’s definition of taste.
- “It Depends” Is the Phrase I Hate MostMany engineers end a discussion with “it depends.” But to me, what matters most is whether a discussion can actually move forward.
- Are You a Critic?Being a cynical critic feels great and makes you feel superior, but in the end you’ll realize it leaves you with nothing but emptiness.
- Why Company Stage MattersMany people use terms like startup, growth stage, and stable stage to describe companies, but these words are too vague to serve as useful criteria. What is this company surviving on right now? How does it grow? What is its most painful problem? If you understand company stage, you’ll know what problems you’re solving every day, and whether this company is actually a good fit for you.