Great post by Dare, Scalability: I Don't Think That Word Means What You Think It Does following up on a post from Scott Loganbill at Google about their choice of "scalable" services. Scalability is a funny question. Every application is designed to handle a certain type of architecture - it's usually one of those fundamental sales analysis questions "and how many orders do you typically process a day? How many people do you have working for you". While scalability problems can be due to both technology and design, it's typically design that is the major culprit. (ok, yes, the guy that said he can run a 15,000 transaction a day system in Access - he likely chose the WRONG technology). But everytime I think of scalability, I always think of 37 Signal's approach to scalability - in short, "Do you really need 12 servers now if you can run on two for a year?" - note read the comments from David Hansson " ... Not worrying too much about sca...
Solutions for Today; Ready for Tomorrow. Andrew MacNeill's blog about development, technology, Visual FoxPro, databases, community and occasionally, some off-topic discussions.