Scalability Rules (eBook)

Note: CD-ROM/DVD and other supplementary materials are not included.
In their successful first book, The Art of Scalability, AKF Partners cofounders Martin L. Abbott and Michael T. Fisher drew on their unparalleled experience managing some of the world's highest transaction volume Web sites to cover everything IT and business leaders need to know to build smoothly scaling technology infrastructures. Now in Scalability Rules the authors tackle scalability once again, this time breaking it down into 50 rules that must be followed for effective and manageable growth. Few people have effectively scaled their Web platforms to the size of Amazon, Google, eBay, and Facebook. Scalability Rules takes a direct approach by presenting fundamental principles in an easily read and digestible format for rapid application to almost any technical environment. It will be useful to all readers as a primer, a refresher, and as a reference. Its principles can be used to form the basis of architectural strategy for just about any company dealing with hypergrowth in the Web 2.0 world.This book is currently available in Rough Cut format, as the authors write chapters they will be added here. Subscribers will be notified as more chapters become available.

---

50 Powerful, Easy-to-Use Rules for Supporting Hypergrowth in Any Environment Scalability Rules is the easy-to-use scalability primer and reference for every architect, developer, web professional, and manager. Authors Martin L. Abbott and Michael T. Fisher have helped scale more than 200 hypergrowth Internet sites through their consulting practice. Now, drawing on their unsurpassed experience, they present 50 clear, proven scalability rules-and practical guidance for applying them. Abbott and Fisher transform scalability from a "e;black art"e; to a set of realistic, technology-agnostic best practices for supporting hypergrowth in nearly any environment, including both frontend and backend systems. For architects, they offer powerful new insights for creating and evaluating designs. For developers, they share specific techniques for handling everything from databases to state. For managers, they provide invaluable help in goal-setting, decision-making, and interacting with technical teams. Whatever your role, you'll find practical risk/benefit guidance for setting priorities-and getting maximum "e;bang for the buck."e; * Simplifying architectures and avoiding "e;over-engineering"e; * Scaling via cloning, replication, separating functionality, and splitting data sets * Scaling out, not up * Getting more out of databases without compromising scalability * Avoiding unnecessary redirects and redundant double-checking * Using caches and content delivery networks more aggressively, without introducing unacceptable complexity * Designing for fault tolerance, graceful failure, and easy rollback * Striving for statelessness when you can; efficiently handling state when you must * Effectively utilizing asynchronous communication * Learning quickly from mistakes, and much more