(Note: This is the second part of a four-part blog post. For Part 1, please click here.)
By Paul Moxon, Senior Director, Product & Solutions Marketing
Ensure scalability and availability
When your multi-tiered application architecture is located on premise, your IT department can configure routers to load-balance connections and inbound traffic across multiple instances of an application; support sticky-user sessions; enable SSL termination (i.e., handle the SSL processing in the router); and provide multiple load-balancing algorithms.
Done right, load balancing spreads the application load across multiple application instances, provides better response times for users, yields increased application availability, and even re-distributes the load over healthy application instances in the event of a failure of a single application instance. While some sessions may occasionally fail or roll back because of an instance failure, the application generally continues to operate unaffected.
Similarly, when your application is in the cloud, you can and should leverage functionality that lets you automatically scale your application according to demand, based on rules you define – such as rules that protect the application against slow response times and guarantee availability by ensuring that enough “healthy” application instances are running.
If you make sure you have this level of scalability and availability in your cloud-hosted application, the likelihood of your application failing due to an unbalanced load or traffic issue is dramatically diminished.
(For Part 3, please click here.)