4 ms·
Here you go https://www.uber.com/en-CA/blog/postgres-to-mysql-migration/ https://www.uber.com/en-CA/blog/postgres-to-mysql-migration/
by betaby 1y ago
Here you go https://www.uber.com/en-CA/blog/postgres-to-mysql-migration/ https://www.uber.com/en-CA/blog/postgres-to-mysql-migration/
- psionides 1y agoYeah so there's basically just that one ;)
- hu3 1y agohttps://engineeringblog.yelp.com/2024/10/migrating-from-postgres-to-mysql.html https://engineeringblog.yelp.com/2024/10/migrating-from-post...
- wredcoll 1y agoYou're not wrong, but this is the tldr: > The DB used is PostgreSQL which is not used anywhere else at Yelp, which meant that only a small rotation of long-tenured employees knew Postgres well enough to do outage response. This caused issues in maintenance, visibility, and outage response times. The teams working on the Restaurants products are not infra teams, and the Yelp-wide infra teams (understandably) focus on Yelp-standard infrastructure. As a result, when we did see issues with Postgres it was often a scramble to find people with relevant expertise. > So, we switched out this DB in-place with a Yelp-standard MySQL DB.
- speed_spread 1y agoIt's a very Uber thing to do to enter a one way from the wrong end.
- DonHopkins 1y agoAt least they have the moxie to flip off people going the right way. https://www.youtube.com/watch?v=Tz6A6t55qXk https://www.youtube.com/watch?v=Tz6A6t55qXk