The Dot Bomb and Its Effect on Building Large Systems
No one likes to lose data. No one likes to have the services they provide be inaccessible. No one likes to clean up messes. No one likes to
The last point is a real
Specifically, at this time in computing we are all just now beginning to recover from the dot-com bubble popping. Inside the bubble, online users had an
Many times, in such initiatives, the architecture is brute-forceda huge investment in hardware and services to compensate for poor or understaffed engineering combined with too-short
In economics, there is a law of
Computers get faster every year. Moore's Law says they double in speed/capacity/performance every 18 months. That sounds great, but when a purchase is made and an architecture is designed, there is a single "market offering." In other words, at the time of the purchase you have a snapshot of a
The "best" technology that can be bought today is expensive. Effectively, at the top end of the performance curve, more and more buys you less and less. So, you can blow your budget on the
Why is this so? During the dot-com era (and even today) companies tend to buy the fastest hardware they can afford in order to "scale." Perhaps by now you can see the fundamental flaw in that
Scalability is the goal, but there are some other commonly overlooked challenges when working with big architectures. The dot com era taught us something that no businessperson would have ever believed before. It taught us that it is possible to take a concept at 8 a.m.; translate that into a business initiative; proceed through design, implementation, testing, and launch; and have millions of customers for that idea by the close of business. That fact that this is possible means that if the business can capitalize on such efficiencies, it will.
Many techniques attempt to handle the issues of rapid development. One such popular approach is that of extreme programming. Regardless of the technique involved, the fact that the solution not only has to work, but it also has to scale dramatically changes the playing field and complicates the rules of the game.
The rest of this book attempts to get you "thinking scalable." We will spend some time first on tried-and-true techniques that can help prevent disaster and speed recovery of mistakes due to rushed timelines or lapses in judgment.
The Art of Scalability: Scalable Web Architecture, Processes, and Organizations for the Modern Enterprise
Scalability Rules: 50 Principles for Scaling Web Sites
Building Scalable Web Sites: Building, Scaling, and Optimizing the Next Generation of Web Applications
The Art of Capacity Planning: Scaling Web Resources