4 ms·
From the linked https://mikecoutermarsh.com/why-infrastructure-engineers-prefer-mysql/ https://mikecoutermarsh.com/why-infrastructure-engineers-pre... > When a
by da39a3ee 5y ago
From the linked https://mikecoutermarsh.com/why-infrastructure-engineers-prefer-mysql/ https://mikecoutermarsh.com/why-infrastructure-engineers-pre...
> When an infrastructure engineer tells you they prefer MySQL. It’s probably because for them it’s simpler/easier to operate it. Backups, replication, failover, upgrades. Accomplishing what is most important to them.
> When product engineers prefer postgres, it’s usually because of something like postgis, jsonb/hstore. Some feature they can use in the app to build something faster.
> I hope this helps in explaining why you often see the infra orgs of many large/high scale companies choose mysql.
Isn't that missing a very important reason which is that
(a) MySQL was better known in the period 2000-2010 when is when many of the large/high scale companies started to create their infrastructure, and
(b) Your choice of database tends to be sticky
- mdasen 5y agoVery good points. I'd add that PostgreSQL didn't even get built-in streaming replication until late 2010 so if you were evaluating anything for a high-availability setup before 2011, you'd be looking at MySQL. As you note, database choices tend to be sticky. PostgreSQL's replication is still a bit of a pain and MySQL has things like Vitess that which offer great tools for scaling out a database (including sharding, replication, etc) PostgreSQL has improved a lot from the 2000-2010 time period, but MySQL still has some good stuff going for it.