|By Rebecca Clinard||
|September 17, 2012 05:00 AM EDT||
Load and performance testing web applications will allow you to determine whether or not your deployment will require a clustered environment. When the test results show that the current throughput is restricted by the capacity of the server but target workloads are not yet met, this is a situation where you can achieve higher scalability by implementing clusters to your environment. Clustering achieves higher scalability by introducing more servers or nodes to expand the capacity of the environment. Obviously, the benefits of adding hardware include higher capacity, reliability, availability, and scalability. But also consider that clustering also adds complexity to your deployment by requiring added maintenance and an increased need for deployment/upgrade automation. To ensure quality of the environment you must always validate your clustered environment and prove out the increased scalability. Use a methodical performance testing approach. Don't try to extrapolate! It's not as easy as "3 nodes in a cluster will support 3x the workload."
An efficiently tuned deployment will, in turn, display an efficient use of server resources (memory, CPU, i/o, etc). Using a cluster increases the number of servers and distributes the workload amongst several servers. This even distribution of the workload can dramatically increase scalability. Not only can this improve the end user experience by reaching higher workloads with predictable response times but it can increase the reliability and stability of the deployment. The cluster acts as a single server so the loss or shutdown of any of the nodes in the cluster will not result in loss of sessions or application data. In the end, the user experience is less frequently interrupted and isn't affected by a single maxed out server or a loss of a server.
When performance or load testing your application uncovers a clear need to introduce clusters or farms to support the target workload, you will want to take into account the following considerations: First you should configure the cluster efficiently for internal maintenance such as data synchronization and heartbeat communications. User sessions which live in memory are more quickly failed over to another node in the cluster instead of persisting them to the database. However, writing the sessions to disk is more permanent which may have its own advantages. Make sure you have tested the performance prices for data synchronization and heartbeat communications. The goal is to configure the cluster to increase scalability with as little overhead as possible.
Load balancers are generally placed out in front of the clusters. These load balancers can be a software solution or a hardware solution. Their job is to distribute the load evenly to the nodes in the cluster. Just as important, LB's reroute traffic when one node of the cluster goes down. This allows for the "transparency" of several servers acting as one. There are several more mature algorithms for distribution than traditional "round robins." Smarter LB's takes into account the CPU and resource usage and overall load of each server and their job is to direct the request to the least loaded server. The number of active users doesn't always equate to more resources being actively used, rather it depends on the types of transactions being executed - lightweight vs. expensive transactions. Smart LB's will detect workload and direct incoming traffic based on resource usage. Often LB's will use sticky sessions based on the client's cookie and/or IP address to route subsequent requests to the same node of cluster where the user session lives. Whenload testing these types of environments, it's a requirement to have a load tool which supports IP Spoofing. This is used to generate the load of many virtual users using multiple IP addresses all from a single machine. Otherwise, the total load would go to a single cluster node.
Types of Clustering
Clustering can be achieved using a few common techniques. Vertical clustering adds capacity to the deployment by installing multiple nodes of a cluster on a single machine. With this approach you must take into consideration the physical limitations of that machine (CPU, memory, i/o) and be careful not over utilize resources; otherwise adding more nodes becomes pointless due to saturation. Horizontal clusters refer to deploying more physical machines. With this approach, each physical machine can run one or more of the nodes of the cluster. Cloud bursting is a way of having a node both within the LAN and a node in the Cloud to be turned "on" during high volume usage or be strategically placed in different geographical locations. The appropriate technique really depends on the specifics of your environment. If you need more capacity and you have beefy infrastructure servers but do not have enough web servers or app servers to fully utilize the underlying hardware, choose the vertical clustering approach by adding more nodes to the same machine. On the other hand, if more physical resources are needed to handle the workload, then build out a horizontal cluster by adding more hardware and deploying more nodes.
How to Load Test a Cluster?
It's important to take a methodical approach to load testing a clustered environment. Load patterns such as ramping tests allow you to identify the current capacity as well as increased scalability as you add more nodes to the cluster. Remember that doubling the number of nodes in a cluster does not equate to doubling its capacity. Many components impact its performance gain such as the communications between the nodes used to just make the cluster work properly. The resource cost increases dramatically with the number of nodes. Capacity is relative and is dependent on myriad other components within the infrastructure. For example, adding another node to the cluster may give the application layer 2x the throughput (although this is not really possible due to "housekeeping" from internal administration overhead to maintain that cluster), but let's say the single webserver out front is already using all its worker threads, then requests will be queued while waiting for a thread to become available and overall throughput will not increase. Only through the analysis of load test results will you completely understand the increased scalability effects of a cluster. Consider another scenario: You have identified a need for building out a cluster of application servers, however you deploy too many nodes resulting in a backlog of requests on the shared database. Performance and load testing will uncover this vulnerability and many other potential scenarios that could otherwise go undetected. Having a comparison analysis feature built right into the load tool will allow you to run tests back to back, after turning on/off nodes in the cluster, and quickly visualize the differences. Also, having the tool with a built-in cloud load generation feature will save time and money setting up and maintaining the performance architecture environment, especially for high load tests.
The Right Approach?
Adding clustering to a deployment allows a web application to achieve higher workloads and gives the advantage of higher availability. However, you must conduct performance tests in order to build out an efficient cluster which meets your goals. Don't forget to weigh the benefits vs. added maintenance complexity/cost. Clusters require a high level of expertise to implement and maintain so they aren't the best solution in every situation. Make sure all moving parts are documented and insist on a complete architectural diagram for future systems administrators (diagrams to include hierarchical transaction pathways as well as location of each node in the cluster including the admin consoles). In the end it's all about delivering the best possible end user experience and in many cases clustering is an excellent solution for increasing scalability of your web deployments.
The battle over bimodal IT is heating up. Now that there’s a reasonably broad consensus that Gartner’s advice about bimodal IT is deeply flawed – consensus everywhere except perhaps at Gartner – various ideas are springing up to fill the void. The bimodal problem, of course, is well understood. ‘Traditional’ or ‘slow’ IT uses hidebound, laborious processes that would only get in the way of ‘fast’ or ‘agile’ digital efforts. The result: incoherent IT strategies and shadow IT struggles that lead ...
Feb. 7, 2016 05:00 PM EST Reads: 432
SYS-CON Events announced today that Commvault, a global leader in enterprise data protection and information management, has been named “Bronze Sponsor” of SYS-CON's 18th International Cloud Expo, which will take place on June 7–9, 2016, at the Javits Center in New York City, NY, and the 19th International Cloud Expo, which will take place on November 1–3, 2016, at the Santa Clara Convention Center in Santa Clara, CA. Commvault is a leading provider of data protection and information management...
Feb. 7, 2016 03:30 PM EST Reads: 376
SYS-CON Events announced today that VAI, a leading ERP software provider, will exhibit at SYS-CON's 18th International Cloud Expo®, which will take place on June 7-9, 2016, at the Javits Center in New York City, NY. VAI (Vormittag Associates, Inc.) is a leading independent mid-market ERP software developer renowned for its flexible solutions and ability to automate critical business functions for the distribution, manufacturing, specialty retail and service sectors. An IBM Premier Business Part...
Feb. 7, 2016 02:00 PM EST Reads: 562
SYS-CON Events announced today that Alert Logic, Inc., the leading provider of Security-as-a-Service solutions for the cloud, will exhibit at SYS-CON's 18th International Cloud Expo®, which will take place on June 7-9, 2016, at the Javits Center in New York City, NY. Alert Logic, Inc., provides Security-as-a-Service for on-premises, cloud, and hybrid infrastructures, delivering deep security insight and continuous protection for customers at a lower cost than traditional security solutions. Ful...
Feb. 7, 2016 01:45 PM EST Reads: 365
In most cases, it is convenient to have some human interaction with a web (micro-)service, no matter how small it is. A traditional approach would be to create an HTTP interface, where user requests will be dispatched and HTML/CSS pages must be served. This approach is indeed very traditional for a web site, but not really convenient for a web service, which is not intended to be good looking, 24x7 up and running and UX-optimized. Instead, talking to a web service in a chat-bot mode would be muc...
Feb. 7, 2016 01:15 PM EST Reads: 190
SYS-CON Events announced today that Catchpoint Systems, Inc., a provider of innovative web and infrastructure monitoring solutions, has been named “Silver Sponsor” of SYS-CON's DevOps Summit at 18th Cloud Expo New York, which will take place June 7-9, 2016, at the Javits Center in New York City, NY. Catchpoint is a leading Digital Performance Analytics company that provides unparalleled insight into customer-critical services to help consistently deliver an amazing customer experience. Designed...
Feb. 7, 2016 01:00 PM EST Reads: 334
The (re?)emergence of Microservices was especially prominent in this week’s news. What are they good for? do they make sense for your application? should you take the plunge? and what do Microservices mean for your DevOps and Continuous Delivery efforts? Continue reading for more on Microservices, containers, DevOps culture, and more top news from the past week. As always, stay tuned to all the news coming from@ElectricCloud on DevOps and Continuous Delivery throughout the week and retweet/favo...
Feb. 7, 2016 12:30 PM EST Reads: 173
SYS-CON Events announced today that Interoute, owner-operator of one of Europe's largest networks and a global cloud services platform, has been named “Bronze Sponsor” of SYS-CON's 18th Cloud Expo, which will take place on June 7-9, 2015 at the Javits Center in New York, New York. Interoute is the owner-operator of one of Europe's largest networks and a global cloud services platform which encompasses 12 data centers, 14 virtual data centers and 31 colocation centers, with connections to 195 ad...
Feb. 7, 2016 11:30 AM EST Reads: 349
[session] From Build to Scale: Lifecycle of Microservices By @fortyfivan | @CloudExpo #Microservices
More and more companies are looking to microservices as an architectural pattern for breaking apart applications into more manageable pieces so that agile teams can deliver new features quicker and more effectively. What this pattern has done more than anything to date is spark organizational transformations, setting the foundation for future application development. In practice, however, there are a number of considerations to make that go beyond simply “build, ship, and run,” which changes ho...
Feb. 7, 2016 10:45 AM EST Reads: 157
SYS-CON Events announced today that AppNeta, the leader in performance insight for business-critical web applications, will exhibit and present at SYS-CON's @DevOpsSummit at Cloud Expo New York, which will take place on June 7-9, 2016, at the Javits Center in New York City, NY. AppNeta is the only application performance monitoring (APM) company to provide solutions for all applications – applications you develop internally, business-critical SaaS applications you use and the networks that deli...
Feb. 7, 2016 10:00 AM EST Reads: 351
If we look at slow, traditional IT and jump to the conclusion that just because we found its issues intractable before, that necessarily means we will again, then it’s time for a rethink. As a matter of fact, the world of IT has changed over the last ten years or so. We’ve been experiencing unprecedented innovation across the board – innovation in technology as well as in how people organize and accomplish tasks. Let’s take a look at three differences between today’s modern, digital context...
Feb. 7, 2016 07:00 AM EST Reads: 165
Continuous Delivery and Release Automation for Microservices By @Anders_Wallgren | @DevOpsSummit #Microservices
As software organizations continue to invest in achieving Continuous Delivery (CD) of their applications, we see increased interest in microservices architectures, which–on the face of it–seem like a natural fit for enabling CD. In microservices (or its predecessor, “SOA”), the business functionality is decomposed into a set of independent, self-contained services that communicate with each other via an API. Each of the services has their own application release cycle, and are developed and depl...
Feb. 6, 2016 02:00 PM EST Reads: 212
At the heart of the Cloud Native model is a microservices application architecture, and applying this to a telco SDN scenario offers enormous opportunity for product innovation and competitive advantage. For example in the ETSI NFV Ecosystem white paper they describe one of the product markets that SDN might address to be the Home sector. Vendors like Alcatel market SDN-based solutions for the home market, offering Home Gateways – A virtual residential gateway (vRGW) where service provider...
Feb. 6, 2016 01:00 PM EST Reads: 147
In the Bimodal model we find two areas of IT - the traditional kind where the main concern is keeping the lights on and the IT focusing on agility and speed, where everything needs to be faster. Today companies are investing in new technologies and processes to emulate their most agile competitors. Gone are the days of waterfall development and releases only every few months. Today's IT and the business it powers demands performance akin to a supercar - everything needs to be faster, every sc...
Feb. 6, 2016 09:00 AM EST Reads: 513
With microservices, SOA and distributed architectures becoming more popular, it is becoming increasingly harder to keep track of where time is spent in a distributed application when trying to diagnose performance problems. Distributed tracing systems attempt to address this problem by following application requests across service boundaries, persisting metadata along the way that provide context for fine-grained performance monitoring.
Feb. 5, 2016 03:45 PM EST Reads: 799
Web performance issues and advances have been gaining a stronger presence in the headlines as people are becoming more aware of its impact on virtually every business, and 2015 was no exception. We saw a myriad of major outages this year hit some of the biggest corporations, as well as some technology integrations and other news that we IT Ops aficionados find very exciting. This past year has offered several opportunities for growth and evolution in the performance realm — even the worst failu...
Feb. 3, 2016 10:00 PM EST Reads: 547
Are you someone who knows that the number one rule in DevOps is “Don’t Panic”? Especially when it comes to making Continuous Delivery changes inside your organization? Are you someone that theorizes that if anyone implements real automation changes, the solution will instantly become antiquated and be replaced by something even more bizarre and inexplicable?
Feb. 3, 2016 06:30 PM EST Reads: 315
Welcome to the first top DevOps news roundup of 2016! At the end of last year, we saw some great predictions for 2016. While we’re excited to kick off the new year, this week’s top posts reminded us to take a second to slow down and really understand the current state of affairs. For example, do you actually know what microservices are – or aren’t? What about DevOps? Does the emphasis still fall mostly on the development side? This week’s top news definitely got the wheels turning and just migh...
Feb. 3, 2016 03:00 PM EST Reads: 287
Test automation is arguably the most important innovation to the process of QA testing in software development. The ability to automate regression testing and other repetitive test cases can significantly reduce the overall production time for even the most complex solutions. As software continues to be developed for new platforms – including mobile devices and the diverse array of endpoints that will be created during the rise of the Internet of Things - automation integration will have a huge ...
Feb. 3, 2016 02:00 PM EST Reads: 641
Providing a full-duplex communication channel over a single TCP connection, WebSocket is the most efficient protocol for real-time responses over the web. If you’re utilizing WebSocket technology, performance testing will boil down to simulating the bi-directional nature of your application. Introduced with HTML5, the WebSocket protocol allows for more interaction between a browser and website, facilitating real-time applications and live content. WebSocket technology creates a persistent conne...
Feb. 3, 2016 07:00 AM EST Reads: 313