4 ms·
There are only two options for me: MySQL or Postgres. And using AWS generally means using Aurora. Then the choice is already made. Not hard at all. Yep, my wo
by Shorel 6y ago
There are only two options for me: MySQL or Postgres.
And using AWS generally means using Aurora. Then the choice is already made. Not hard at all.
Yep, my work involves heavy use of SQL and I find it better than the NoSQL insanity.
- orobinson 6y agoJust curious, for what reasons would you choose MySQL over Postgres?
- kenhwang 6y agoPersonally, when I want speed or easy upkeep and intend on doing dumb simple things. Postgres is more featureful, but if you don't intend on using those features, MySQL is consistently faster and historically smoother to update and keep running.
- malinens 6y agoProbably the same way sometimes people choose sqlite versus mysql- simplicity. There are many cons and pros for both of them!
- xorcist 6y agoTraditionally it was because you needed replication or sharding that you didn't have to boil half an ocean for, or at least half decent full text indices. These days however I believe the differences are smaller and in other areas. Most often, you choose a database because of what you application supports and is tested with, not the other way around. Or what your other applications already use. Complete green fields aren't all that common.
- Shorel 6y agoReplication. And our DBAs are already familiar with the gotchas of MySQL. You just have to write queries in a different way (subqueries are slow, so they are to be rewritten as joins).