3 ms·
I'm always confused by people suggesting that the options are to have either MySQL or NoSQL. (Or, as this article suggests, "NewSQL", which I'm desperately hopi
by MostAwesomeDude 15y ago
I'm always confused by people suggesting that the options are to have either MySQL or NoSQL. (Or, as this article suggests, "NewSQL", which I'm desperately hoping will be clarified by its proponents.) Is Pg not an appropriate suggestion for people looking to improve their SQL-based backends?
Edit: The article includes this gem: "The widely accepted problem with MySQL is that it wasn’t built for webscale applications..." Every time I see "webscale", I get the feeling that the author doesn't actually have a great grasp of what's going on. However, this guy did mention ACID, which confuses me. Did we define "webscale" when I wasn't looking?
- jdunck 15y agoStonebraker has a new DB (VoltDB), so his claims and criticisms should be read in that light.
- eropple 15y agoThe question for most isn't really "MySQL or NoSQL", but "ACID or not." For most people, ACID means MySQL because PostgreSQL (despite my own affection for it) is a major, major pain in the ass to work with on a smaller scale (edit: and Oracle costs more than most programmers' houses, so that tends to rule it out in a lot of cases). PostgreSQL tooling is considerably worse than MySQL (phpMyAdmin is damn near ubiquitous and has no reasonable pgsql competitor). Documentation expects you to already be a guru. And there's often just no really compelling performance reason to pick it over MySQL. And then, when you get to Facebook's scale--though as a coworker just pointed out, Facebook probably isn't particularly ACID-compliant--Postgres is going to have problems that are pretty much the same as those you see in MySQL. PostgreSQL isn't really "better than" or "an improvement over" MySQL. Different tools, different tasks--though they do have considerable overlap.