4 ms·
This comes across as a bit defensive and snarky. I'm not sure what it's hoping to achieve. The not so subtle message, reading between the lines, is that Uber en
by foldr 10y ago
This comes across as a bit defensive and snarky. I'm not sure what it's hoping to achieve. The not so subtle message, reading between the lines, is that Uber engineers had bad experiences with postgres because they are morons. Well, maybe. But my main take away from that is that postgres is hard to use correctly, which if true is actually a good reason not to use it.
If only programmers could be polite to each other occasionally.
- hartator 10y agoCome on, it's fun. Programming can be so boring, a little passion and trolling can't hurt too much.
- merb 10y agoIt's not harder to use than MySQL. And for everything (even MySQL) the rule of thumb is: if you are not confident with the technology don't use it or let somebody else manage it.
- foldr 10y agoSure, I wasn't making a claim about how easy to use postgres actually is. My point was that these slides give the impression (I assume inadvertently) that postgres is difficult to use by making fun of Uber engineers' alleged inability to use it correctly.
- merb 10y agowell if my system spwans new database connection in an open transaction, than you have more problems than just your database. they even had another talk where they let their master die, but just ignoring "free space left on device" messages. Well even Skype could've handled PostgreSQL and they probably had a smaller pool of engineers.
- foldr 10y agoI'm not a big fan of Uber as a company and I don't necessarily think that their engineering team is the shit (I really don't know). But my heuristic here is "any problem that Uber engineers aren't smart enough to avoid is a problem that I might very well face myself".
- merb 10y agowell I think a lot of problems arise in these fast running companies. a company that scale's up slowly and brings their tech stack up and forward with a small team that slowly adds people (so that everybody can learn from people working a little bit longer on the stack) will lead to a way more sane teck stack than a extremly fast growing team + technology. also I loved some talks about instagram. (https://de.slideshare.net/iammutex/scaling-instagram https://de.slideshare.net/iammutex/scaling-instagram) Scaling: replacing all components of a car while driving it at 100mph (And the end slides 150+ are awesome, too). And while they use PostgreSQL and talk about everything, they also did engineering quite right and prolly that's the problem of Uber. They tried to get to big to fast and know everything burns (not just their tech).
- ldrndll 10y agoI'm not so sure that's an appropriate heuristic here. The problems they faced were partly a result of scale[1]. Most companies with scaling problems of the same magnitude as Uber have engineers competent enough to correctly handle the issues they cited as reasons for switching. Honestly, there are hugely people at any number of Postgres consultancies that could have helped them setup logical replication - since they complained about it being difficult to do - which seems like it would have solved many of their issues. I'd like to believe Uber had the resources to do this, if they had cared to. [1] For example, write amplification.
- cookiecaper 10y agoMy reading was less that PostgreSQL was "too difficult to use" and more that MySQL is less strict about safety. That difference is more substantial than it may sound. "An ounce of prevention is worth a pound of cure", as they say. While PostgreSQL may do things in a way that require a little extra annoyance up front, they're usually that way to prevent disastrous data integrity issues further down the line. What can you say when someone says things like "We prefer logical replication because it uses less bandwidth"? There are extremely good justifications for the high bandwidth cost of real (bit-level) replication. Logical replication has uses but IMO it should be applied cautiously and sparingly. I felt all of the ASCII shrugs were justified. They signify a tradeoff that Uber made. My personal feeling is that most of those tradeoffs were bad, but what can you do. The slides shrug because you can't argue. If that's the problemset that their organization prefers to deal with, more power to them.
- gdulli 10y agoPostgres is not hard to use correctly and the implication is that Uber didn't make an attempt to clear up certain misunderstandings, not that they wouldn't have been able to. It's not moronic to succumb to using talking points or FUD you've seen in blogs or incompletely-informed personal bias in making decisions. It's just human. Since people are going to keep looking up literature on the topic here's a new higher-quality piece of literature.
- StreamBright 10y agoI do not think that Postgres is hard to use correctly and I also think that Uber did a poor job on trying to fix their problems. This PDF just outlines the details. Uber also has the tendency to switch databases every few years. It is hard for me to take their opionion seriously on databases. https://www.yumpu.com/en/document/view/53683323/migrating-uber-from-mysql-to-postgresql https://www.yumpu.com/en/document/view/53683323/migrating-ub...
- anarazel 10y ago> This comes across as a bit defensive and snarky As somebody who works on postgres a good chunk of his time, I agree. I preferred the initial type of responses (where we just looked into the valid complaints and disregarded other angles). But everyone can speak about something like this, and that's good too.
- grzm 10y agoHaving just read through the slide deck, I'm having a hard time coming to the same conclusion you do. Overall, I thought it was quite balanced, pointing out strengths and weaknesses of both MySQL and PostgreSQL. The author even started out with a slide with Inigo Montoya, "You insulted my elephant. Prepare to die", so he was clearly cognizant of the fact that this could be taken as purely a blind defense of PostgreSQL, and that is not the intent. Would you mind taking the time to point out what phrases or slides gave you the impression that this was written from the position that "Uber engineers had bad experiences with postgres because they are morons"? I know that different people can get different impressions of the same material, so it would be helpful for me to understand better what gave you that impression. There are a couple of comments like: > I assume the company the size of Uber can figure it out. C’mon > But... c’mon. Uber? Both of these I think reflect the idea that it's likely Uber would have been able to continue to use Postgres if they were interested in fixing the issues they had with the system, rather than had additional, other motivations for doing so, the belief being that the Postgres-specific issues they list are likely soluble if they had wanted to put in the effort. They're a large enough organization that they should have had the resources to do so. That doesn't mean that their decision to move off of Postgres for those other reasons wasn't the right thing to do: just that there's not enough information there for us to really understand the decision process. From a Postgres community standpoint, it's important to make sure that they have quality answers to the issues publicly raised by very visible companies such as Uber. Many people will read about Uber's experience with Postgres, and it makes sense for the Postgres community to be clear what can be done about them. Your point about "postgres is hard to use correctly" I think is one of those things that it's hard to use a lot of the systems out there—not just Postgres—at the scale that Uber or some of the other large installations do. That's when you really become aware of where the stresses put on the systems start to show and what you need to be aware of to tune and set them up correctly for your use case. Overall, I think 'gdulli's response (https://news.ycombinator.com/item?id=14223170 https://news.ycombinator.com/item?id=14223170) is largely on point. Like I said above, if you'd point out which parts struck you as particularly unfair, I know I'd benefit from it to hear more from your perspective.
- foldr 10y agoI found the use of shrug emojis in response to substantive points from the Uber paper pretty infuriating. I didn't say that postgres is difficult to use. I said that the slides give that impression.