Re:Twitter Shifting More Code to JVM, Citing Performance and...
by eropple on Monday July 04, 2011 @03:35PM
(#2727583)
True. That said, designing for scalability isn't that hard, and does not take that much more time than just bunging out whatever comes first to mind.
Re:Twitter Shifting More Code to JVM, Citing Performance and...
by jshen on Tuesday July 05, 2011 @01:43AM
(#2728781)
You're assuming that you know ahead of time what the bottlenecks are, and more importantly, which trade offs to make, because scaling is almost always about trade offs.
A scalable solution is usually a more rigid solution as well, and that can be a problem for a startup that may need to try a few ideas before they hit on what works.
However, at the time it might have gone the other way: Perhaps their user base and volume might have increased at a slower place, leaving plenty of time to evolve their scalability, while their user experience might have required relentless change.
In which case, they should have planned for their user experience to "scale" rather than their infrastructure.