3 ms·
Still blows my mind that it took Uber so long to migrate away from a single db solution. The bit about wanting an event system to handle downstream trip process
by whalesalad 9y ago
Still blows my mind that it took Uber so long to migrate away from a single db solution. The bit about wanting an event system to handle downstream trip processing w/o having one failure block the whole job was shocking.
I’m all for avoiding premature optimization but this was taken to the extreme.
PostgreSQL is capable of all of this out of the box. Wonder why a custom tool was built instead?
- sidlls 9y agoPerhaps they had an existing system they thought might cost more to rewrite with a different DB.
- subway 9y agoStill blows my mind that it took Uber so long to migrate away from a single db solution. The bit about wanting an event system to handle downstream trip processing w/o having one failure block the whole job was shocking. I'm pretty sure they've seen a few iterations on their data stores. I remember attending a meetup at Urban Airship in 2012 or so where Uber engineers gave a presentation about a data store migration (I think from Mongo to MySQL)
- mangatmodi 9y agoAbout postgres: Uber has bashed it really bad here https://eng.uber.com/mysql-migration/ https://eng.uber.com/mysql-migration/
- gaius 9y agoPostgreSQL is capable of all of this out of the box. Wonder why a custom tool was built instead? They have over-hired engineers is the obvious answer.