The Perfect Match - Apache 2.2 & Tomcat 6.0
Introduction to Horizontal & Vertical Scaling
HA and LB Practical Example
High Availability Application is deployed in each of
Server enables seamless failover
and state management Nodes
System is always ready and available to serve users.
Tolerates and overcomes faults and continues operating normally
in the event of failure of some of its components.
If the system experiences a failure, it continues to operate
without interruption during the repair process.
Load Balancing All these nodes will be used under
heavy load. Work is distributed and
allotted by the server
Request 1 Request N
More Users Distributes work across all nodes
Load is distributed evenly across all the available nodes.
The node server ensures no node is overloaded and no node is too
More nodes can be added without downtime or interruption.
The Perfect Match - Apache 2 & Tomcat 6
Apache is free & open source. Designed to provide a balance of
flexibility, portability, and performance.
Apache is the first web server software to surpass the 100 million web
site milestone, so its the most-used Web server software package on
Tomcat 6 is an open source servlet container developed by the
Apache Software Foundation.
Horizontal and Vertical Scaling
Vertical Scaling: (Otherwise known as scaling up) means to add more hardware resources to the same
machine, generally by adding more processors and memory.
• Easy to implement
• Single point of failure
Horizontal Scaling: (Otherwise known as scaling out) means to add more machines into the
mix, generally cheap commodity hardware.
• Cheaper - at least more linear expenditures
• Hard to implement
• Many points of failure and therefore can usually handle