SQL Databases Don't Scale
adam.heroku.com
SQL Databases Don't Scale
1–10 of 34 posts
Re: SQL Databases Don't Scale
#2Re: SQL Databases Don't Scale
#3Claiming that SQL databases don't scale, especially using MySQL as the example, is simply ignorant. Oracle, DB2, SQL Server all scale to handle databases orders of magnitude bigger than anything the most successful RoR app is running.
Re: SQL Databases Don't Scale
#4It's not that SQL databases do not scale per se, they just can't arbitrarily scale.
Most applications today manage pretty well with nothing more than sharding and replication. Sure, it's not the optimal solution, and it's not easy - but it gets the job done.
Facebook, at the very core (behind all the layers of cache), run, arguably, the largest MySQL landscape in the world - and they seem to be doing pretty good.
Until Heroku comes up with a better solution (or a better question), TFA is no more than flamebait.
Re: SQL Databases Don't Scale
#5Re: SQL Databases Don't Scale
#6Re: SQL Databases Don't Scale
#7Re: SQL Databases Don't Scale
#8Re: SQL Databases Don't Scale
#9I can't count how many Rails fanboys have written this same article. What do they think big companies, banks, government agencies -- organizations with huge databases -- use? What kind of database do the RoR developers think the real world runs on? Claiming that SQL databases don't scale, especially using MySQL as the example, is simply ignorant. Oracle, DB2, SQL Server all scale to handle databases orders of magnitu…
This gets especially critical once you stop assuming that data can be centralised. Once your required transactional context needs to scale large areas (geographically or logically) then the overhead of this is mighty. 2PC itself does not scale indefinitely, and while interesting research is being done in alternative transactional approaches, it would be tough to argue that any are acceptable solutions to the problem.
Also your example of banks is perhaps not an ideal one. While banks may indeed run some very large databases, they don't run one HUGE database which is expected to be always consistent. Things like ATM systems etc. run based on eventual consistency and tolerance favouring availability precisely because a simple horespower approach to a transactional database (whether SQL or not) wouldn't currently work in this domain.
Re: SQL Databases Don't Scale
#10It's also hellishly complicated, but so is the problem.