3 ms·
I definitely agree that in most cases Postgres is still superior to MySQL (feature maturity and variety, reliability, ...). There's just one problem: (to my kno
by chaostheory 19y ago
I definitely agree that in most cases Postgres is still superior to MySQL (feature maturity and variety, reliability, ...). There's just one problem: (to my knowledge) there is currently no such thing as an open source clustered version of postgres. (There is a non-free clustered version, but it's not mature and its cost is prohibitive to small businesses.)
MySQL, even with its problems, is good enough. Moreover it accounts for future growth with MySQL Cluster. While MySQL Cluster is not yet mature (though this may change soon), it's there, it's open, and it's why I chose MySQL for my startup, even though I'm a Postgres veteran.
The problem with Postgres (and most databases without clustering) is when you need more resources your only option is to buy a bigger box to replace your current one. Eventually you'll have to buy specialized and super pricey machines...
With clustering you can add x-number of cheap commodity boxes to the existing set to meet your current needs.
- mattculbreth 19y agoThese are good points, but from what I'm seeing it's now more in vogue to use sharding (or other favorite term for same) to split your data by user across different DBs. That way you can still scale horizontally.
- chaostheory 19y agointeresting, I'm not a sysadmin guy so could you explain the differences between clustering and sharding from a db standpoint? Is there an open source sharding solution for Postgres?
- mattculbreth 19y agoWell clustering is having multiple servers addressing the same content. Boosts performance and reliability. Sharding is where you split the data across multiple servers, based on some identifying category like users, functional area, etc.
- dood 19y agoA little on sharding: An Unorthodox Approach to Database Design : The Coming of the Shard [http://news.ycombinator.com/item?id=38407 http://news.ycombinator.com/item?id=38407] Partitioning vs. Federation vs. Sharding [http://www.lethargy.org/~jesus/archives/95-Partitioning-vs.-Federation-vs.-Sharding.html http://www.lethargy.org/~jesus/archives/95-Partitioning-vs.-...]
- cpinto 19y agoCheck pgpool-ii: http://pgpool.projects.postgresql.org/pgpool-II/en/ http://pgpool.projects.postgresql.org/pgpool-II/en/
- epi0Bauqu 19y agoBy non-free clustered version, are you referring to Slony (http://slony.info/ http://slony.info/) ? I believe you can use it for free, and I have known people who use it successfully in production.
- zach 19y agoThat's how the Reddits did it.
- davidw 19y agoThey use Postgres? I hadn't seen that before.
- dood 19y agoFrom 11 months ago: [http://programming.reddit.com/info/jl2a/comments/cjpfw http://programming.reddit.com/info/jl2a/comments/cjpfw] " We use postgresql + slony, and are fairly pleased. Most of the time reddit slows down, it's db related, but so far there has always been a way to work through it. That being said, I feel we have to spend far too much time worrying about the database, and that's probably the situation with any relational db. Presently, we have a db master that replicated to one machine, and that second machine replicates to a couple others. Most of the reddit queries are handled by the master and the first slave. The other slaves are used for backups and slow queries (e.g. stats and recommendations). Replication and query load-balancing helped out a lot with the database load, but it introduced a new host of problems. Replication lag, in particular. This occurs when a db write is committed to the master, but the next read hits a slave before the write has propagated. "
- deleted 19y ago[deleted]