All of these response posts seem to miss one big piece that made no sense to me. Uber goes really in-depth around the higher cost of updates in postgres, but then Uber describes Schemaless as an immutable append only data store. They created a custom database with no updates, but one of their primary reasons for changing from postgres to mysql was because of the high cost of updates?
On Uber’s Choice of Databases
11–15 of 15 posts
Re: On Uber’s Choice of Databases
#12Sure, for that VERY specific (and not very common) use case U-Hauls beat F-150s. However, I think we can all agree that F-150s are far more versitle for most use cases, up to including something trivial like heading to Starbucks for a quick coffee.
Re: On Uber’s Choice of Databases
#13All of these response posts seem to miss one big piece that made no sense to me. Uber goes really in-depth around the higher cost of updates in postgres, but then Uber describes Schemaless as an immutable append only data store. They created a custom database with no updates, but one of their primary reasons for changing from postgres to mysql was because of the high cost of updates?
From what I can tell Schemaless has updates but represents them as inserts. When you want to change something (e.g. change the billing status of a trip), it writes a new billing status for the trip and consumers will always ask for the latest billing status for the trip, which is the most recent and up-to-date one. Take this with a grain of salt, I just read the Schemaless articles yesterday.
Re: On Uber’s Choice of Databases
#14This is a very good and fair response and anyone serious about tuning their DB should have use-the-index-luke.com bookmarked!
Re: On Uber’s Choice of Databases
#15This is a very good and fair response and anyone serious about tuning their DB should have use-the-index-luke.com bookmarked!