Scalability & High Availability

Other Refcardz

Core .NET

Features include Common .NET Types, Formatting Strings, Declaring Events, Generics, Query Expressions (C# 3), Tips and more.

Agile Adoption: Decreasing Time to Market

About Agile Adoption, What Agile Practices Improve Time to Market, How to Adopt Agile Strategies Successfully, and Next Steps...

Core Java Concurrency

Contents Include: About Java Concurrency, Concepts, Protecting Shared Data, Concurrent Collections, Threads, Threads Coordination and more...

Windows PowerShell

Features The Language, Operators, Basic Tasks—Text and Files, Types and Objects, Building Custom Objects, Hot Tips and more...

"This is a very good concept, and will be useful to people new to PowerShell." --Marco Shaw, MVP - Windows Server – Admin Frameworks

Click Here To
Download PDF

Overview

These days the words Scalability and Availability are thrown around so often that often it is difficult to know what they actually mean in each case. This DZone Refcard provides you with the tools to define these terms so that your team can implement mission-critical systems with well-understood performance goals. Contents include: An Overview of Scalability and High Availability, Implementing Scalable Systems, Caching Strategies, Clustering, Redundancy and Fault Tolerance, Hot Tips, and More...

About the Author

Eugene Ciurana is an open-source evangelist who specializes in the design and implementation of mission-critical, high-availability large scale systems. As Director of Systems Infrastructure, he and his team designed and built a 100% SOA and cloud system that enables millions of Internet-ready educational and handheld products and services. As chief liaison between Walmart.com Global and the ISD Technology Council, he led the official adoption of Linux and other open-source technologies at Walmart Stores Information Systems Division. He’s also designed high performance systems for major financial institutions and many Fortune 100 companies in the United States and Europe.

Publications
Developing with the Google App Engine
Best Of Breed: Building High Quality Systems, Within Budget, On Time, and Without Nonsense
The Tesla Testament: A Thriller

Web site
http://eugeneciurana.com

Comments

govind naroji replied on Wed, 2009/03/11 - 3:22pm

Thanks a lot for this Ref card. For a long time I wanted to clear my concepts on scalability and stuff - this surely helped to get the knowledge real quick.

rahulhinge replied on Fri, 2009/04/17 - 2:29pm

Hi,
How can we ensure the transaction scalability at design time. For example, Customer is expecting system to support 100000 transactions per minute. If the developed and deployed system proved to be unable to handle 100000 trx/minute then there is high penalty clause. I don't have a luxury to create actual prototype or POC. In this case how should I ensure transaction scalability and satisfy customer?
Thanks and Regards,
Rahul

y9_@live.com replied on Tue, 2009/10/06 - 3:04pm

Hi, How can we ensure the transaction scalability at design time. For example, Customer is expecting system to support 100000 transactions per minute. If the developed and deployed system proved to be unable to handle 100000 trx/minute then there is high penalty clause. I don't have العاب منتديات a luxury to create actual prototype or POC. In this case how should I ensure transaction scalability and satisfy customer? Thanks and Regards, haytham