4 ms·
Why Uber Engineering Switched from Postgres to MySQL | https://news.ycombinator.com/item?id=12166585 https://news.ycombinator.com/item?id=12166585 Re: Why Uber
by j_s 9y ago
Why Uber Engineering Switched from Postgres to MySQL | https://news.ycombinator.com/item?id=12166585 https://news.ycombinator.com/item?id=12166585
Re: Why Uber Engineering Switched from Postgres to MySQL | https://news.ycombinator.com/item?id=12179222 https://news.ycombinator.com/item?id=12179222
Why we lost Uber as a user | https://news.ycombinator.com/item?id=12201353 https://news.ycombinator.com/item?id=12201353
> naming / pronunciation diversion: https://news.ycombinator.com/item?id=12201672 https://news.ycombinator.com/item?id=12201672
- dx034 9y agoI never understood which table caused these issues at Uber. They use an example with birthday changes for users. That's no real world example. Apparently issues were caused by a small table updated 500+ times a second and used in a lot of joins. That could be the driver table but why would they update it so much? Personal information rarely changes and live information about the driver (trip status, position, online/offline) should be stored separate from that? And you wouldn't need transactions around those updates? Did they ever clarify what data actually caused the issues?
- merb 9y agoplease don't use uber as an example. they made just so many mistakes with postgresql (mistakes that would probably blow up a ton of databases including mysql)
- technion 9y agoThe fact is there are decision makers - often non-technical ones - who do look at Uber as an example. It's something we should at least consider an issue, even if it doesn't feel like a valid technical issue.