Saturday, 14th April 2007
My “why move away from SGML?” reason is the way that every time I have to explain to someone that their Mozilla bug in invalid because HTML is actually an SGML application [...] I finish up by saying “if you want to see the actual spec that I’ve been told says that, you can buy a copy for 230 Swiss francs.”
In the big picture, Twitter did exactly the right thing. They had a good idea and they buckled down and focused on delivering something as cool as possible as fast as possible, and it’s really hard, in early 2007, to beat Rails for that. When all of a sudden there were a few tens of thousands of people using it, then they went to work on the scaling.
The promise [of J2EE] was that of infinite scalability based on tooling, which assumes that designing scalable systems is a general case problem. I now firmly believe that this is flawed reasoning. Frameworks don’t solve scalability problems, design solves scalability problems.
Rails and Scaling with Multiple Databases. Ryan Tomayko explains how his team spreads a high traffic Rails application across five separate PostgreSQL databases by giving each client their own schema—similar to how WordPress MU scales. # 2:32 am