5 ms·

MySQL has had solid and flexible replication options for a long time. Postgres has only just started to catch up in the last couple of years. Don't get me wron

by darkr 10y ago

MySQL has had solid and flexible replication options for a long time. Postgres has only just started to catch up in the last couple of years. Don't get me wrong, I would generally choose Postgres over MySQL for an RDBMS with replication requirements these days, but I'm not sure I would have made that same descion a few years ago. There are valid reasons that long established companies such as Google, Twitter, Facebook and countless others chose MySQL as their primary data store.

dijit 10y ago
it's not that "replication options just started to catch on" with postgresql, it was that when the postgresql team take something into core it has to be fully fleshed out and fully supported with no surprises. And with that in mind, I would take the slow to deliver replication options postgresql supplies in base over the previous third-party options which where comparable to the built-in options in mysql... and I'd take it over mysql's built-in options. and I've used both postgresql and mysql in highly transactional/reliable production environments for over 5 years.
dunk010 10y ago
> There are valid reasons that long established companies such as Google, Twitter, Facebook and countless others chose MySQL as their primary data store. I think you're misrepresenting things here. While all do use MySQL for some specific tasks, it's clear that all also have many other central datastores which are not MySQL. In Google's case this is a gross overstatement.
- spotman 10y ago
  Not really, YouTube runs on MySQL. Pretty sure it's still the largest video site in the world.
  - mdani 10y ago
    YouTube runs several MySQL instances behind Vitess (source: http://blog.vitess.io/2015/03/scaling-mysql-in-cloud-with-vitess-and.html http://blog.vitess.io/2015/03/scaling-mysql-in-cloud-with-vi... )
  - secure 10y ago
    At the same time, YouTube is only one of Google’s services, and there is no evidence that the remaining services run on MySQL as well.
- niccaluim 10y ago
  Twitter's underlying data stores are and always have been MySQL.
kriro 10y ago
I guess I'll be "that guy" who brings up non-technical concerns. I'd think very long and hard about using MySQL these days. Oracle is pretty much bizzaro treating it and widening the feature gap between the open source and enterprise version. Wikimedia is using MariaDB so I'd guess it works well for certain high scale use cases. [I know there's different opinions but I'd rather have a fully open database if I have a choice. For the record I default to PostgreSQL]

by darkr 10y ago

dijit 10y ago

it's not that "replication options just started to catch on" with postgresql, it was that when the postgresql team take something into core it has to be fully fleshed out and fully supported with no surprises. And with that in mind, I would take the slow to deliver replication options postgresql supplies in base over the previous third-party options which where comparable to the built-in options in mysql... and I'd take it over mysql's built-in options. and I've used both postgresql and mysql in highly transactional/reliable production environments for over 5 years.

dunk010 10y ago

> There are valid reasons that long established companies such as Google, Twitter, Facebook and countless others chose MySQL as their primary data store. I think you're misrepresenting things here. While all do use MySQL for some specific tasks, it's clear that all also have many other central datastores which are not MySQL. In Google's case this is a gross overstatement.

spotman 10y ago
Not really, YouTube runs on MySQL. Pretty sure it's still the largest video site in the world.
- mdani 10y ago
  YouTube runs several MySQL instances behind Vitess (source: http://blog.vitess.io/2015/03/scaling-mysql-in-cloud-with-vitess-and.html http://blog.vitess.io/2015/03/scaling-mysql-in-cloud-with-vi... )
- secure 10y ago
  At the same time, YouTube is only one of Google’s services, and there is no evidence that the remaining services run on MySQL as well.
niccaluim 10y ago
Twitter's underlying data stores are and always have been MySQL.

kriro 10y ago

I guess I'll be "that guy" who brings up non-technical concerns. I'd think very long and hard about using MySQL these days. Oracle is pretty much bizzaro treating it and widening the feature gap between the open source and enterprise version. Wikimedia is using MariaDB so I'd guess it works well for certain high scale use cases. [I know there's different opinions but I'd rather have a fully open database if I have a choice. For the record I default to PostgreSQL]