On Saturday, July 30, 2016 06:38:01 AM Rich Freeman wrote: > On Sat, Jul 30, 2016 at 6:24 AM, Alan McKinnon <alan.mckin...@gmail.com> wrote: > > On 29/07/2016 22:58, Mick wrote: > >> Interesting article explaining why Uber are moving away from PostgreSQL. > >> I am > >> running both DBs on different desktop PCs for akonadi and I'm also > >> running > >> MySQL on a number of websites. Let's which one goes sideways first. :p > >> > >> https://eng.uber.com/mysql-migration/ > > > > I don't think your akonadi and some web sites compares in any way to Uber > > and what they do. > > > > FWIW, my Dev colleagues support and entire large corporate ISP's > > operational and customer data on PostgreSQL-9.3. With clustering. With no > > db-related issues :-) > > Agree, you'd need to be fairly large-scale to have their issues,
And also have to design your database by people who think MySQL actually follows common SQL standards. > but I > think the article was something anybody interested in databases should > read. If nothing else it is a really easy to follow explanation of > the underlying architectures. Check the link posted by Douglas. Ubers article has some misunderstandings about the architecture with conclusions drawn that are, at least also, caused by their database design and usage. > I'll probably post this to my LUG mailing list. I think one of the > Postgres devs lurks there so I'm curious to his impressions. > > I was a bit surprised to hear about the data corruption bug. I've > always considered Postgres to have a better reputation for data > integrity. They do. > And of course almost any FOSS project could have a bug. I > don't know if either project does the kind of regression testing to > reliably detect this sort of issue. Not sure either, I do think PostgreSQL does a lot with regression tests. > I'd think that it is more likely > that the likes of Oracle would (for their flagship DB (not for MySQL), Never worked with Oracle (or other big software vendors), have you? :) > and they'd probably be more likely to send out an engineer to beg > forgiveness while they fix your database). Only if you're a big (as in, spend a lot of money with them) customer. > Of course, if you're Uber > the hit you'd take from downtime/etc isn't made up for entirely by > having somebody take a few days to get everything fixed. -- Joost
