> Nearly everything else in Postgres is set-it-and-forget-it.
There are many people who would disagree with that. Talking to Uber engineers would probably be a good idea to dispel that myth.
There are many people who would disagree with that. Talking to Uber engineers would probably be a good idea to dispel that myth.
Nobody is saying MySQL is a bad key-value store!
Many of the NoSQL databases have provisions for these situations so they can handle both writes but bubble the decision up to the application layer. CouchDB, for instance, will tell you you've got multiple versions and has a way for you to tell it how to resolve the conflict. CRDTs let you bake the logic in for handling a conflict. MySQL does not do any of that. If your database consists of "likes" and other low-value data like that, you may not care if you're losing data at some low rate. Reddit is in that situation, and the decision seems to work for them. But I don't think it generalizes to all situations.
not a good idea, somebody who let their database master run out of storage space is probably not a good source.