|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.
When building DevOps or continuous delivery practices you can learn a great deal from others. What choices did they make, what practices did they put in place, and how did they connect the dots? At Sonatype, we pulled together a set of 21 reference architectures for folks building continuous delivery and DevOps practices using Docker. Why? After 3,000 DevOps professionals attended our webinar on "Continuous Integration using Docker" discussing just one reference architecture example, we recogn...
Jan. 22, 2017 10:15 PM EST Reads: 1,419
An overall theme of Cloud computing and the specific practices within it is fundamentally one of automation. The core value of technology is to continually automate low level procedures to free up people to work on more value add activities, ultimately leading to the utopian goal of full Autonomic Computing. For example a great way to define your plan for DevOps tool chain adoption is through this lens. In this TechTarget article they outline a simple maturity model for planning this.
Jan. 22, 2017 08:45 PM EST Reads: 932
The proper isolation of resources is essential for multi-tenant environments. The traditional approach to isolate resources is, however, rather heavyweight. In his session at 18th Cloud Expo, Igor Drobiazko, co-founder of elastic.io, drew upon his own experience with operating a Docker container-based infrastructure on a large scale and present a lightweight solution for resource isolation using microservices. He also discussed the implementation of microservices in data and application integrat...
Jan. 22, 2017 07:15 PM EST Reads: 3,639
In his General Session at DevOps Summit, Asaf Yigal, Co-Founder & VP of Product at Logz.io, will explore the value of Kibana 4 for log analysis and will give a real live, hands-on tutorial on how to set up Kibana 4 and get the most out of Apache log files. He will examine three use cases: IT operations, business intelligence, and security and compliance. This is a hands-on session that will require participants to bring their own laptops, and we will provide the rest.
Jan. 22, 2017 06:30 PM EST Reads: 5,023
Here’s a novel, but controversial statement, “it’s time for the CEO, COO, CIO to start to take joint responsibility for application platform decisions.” For too many years now technical meritocracy has led the decision-making for the business with regard to platform selection. This includes, but is not limited to, servers, operating systems, virtualization, cloud and application platforms. In many of these cases the decision has not worked in favor of the business with regard to agility and cost...
Jan. 22, 2017 06:00 PM EST Reads: 697
All organizations that did not originate this moment have a pre-existing culture as well as legacy technology and processes that can be more or less amenable to DevOps implementation. That organizational culture is influenced by the personalities and management styles of Executive Management, the wider culture in which the organization is situated, and the personalities of key team members at all levels of the organization. This culture and entrenched interests usually throw a wrench in the work...
Jan. 22, 2017 06:00 PM EST Reads: 1,544
As the race for the presidency heats up, IT leaders would do well to recall the famous catchphrase from Bill Clinton’s successful 1992 campaign against George H. W. Bush: “It’s the economy, stupid.” That catchphrase is important, because IT economics are important. Especially when it comes to cloud. Application performance management (APM) for the cloud may turn out to be as much about those economics as it is about customer experience.
Jan. 22, 2017 03:15 PM EST Reads: 4,744
When you focus on a journey from up-close, you look at your own technical and cultural history and how you changed it for the benefit of the customer. This was our starting point: too many integration issues, 13 SWP days and very long cycles. It was evident that in this fast-paced industry we could no longer afford this reality. We needed something that would take us beyond reducing the development lifecycles, CI and Agile methodologies. We made a fundamental difference, even changed our culture...
Jan. 22, 2017 03:00 PM EST Reads: 1,203
Internet of @ThingsExpo, taking place June 6-8, 2017 at the Javits Center in New York City, New York, is co-located with the 20th International Cloud Expo and will feature technical sessions from a rock star conference faculty and the leading industry players in the world. @ThingsExpo New York Call for Papers is now open.
Jan. 22, 2017 02:30 PM EST Reads: 3,760
SYS-CON Events announced today that Dataloop.IO, an innovator in cloud IT-monitoring whose products help organizations save time and money, has been named “Bronze Sponsor” of SYS-CON's 20th International Cloud Expo®, which will take place on June 6-8, 2017, at the Javits Center in New York City, NY. Dataloop.IO is an emerging software company on the cutting edge of major IT-infrastructure trends including cloud computing and microservices. The company, founded in the UK but now based in San Fran...
Jan. 22, 2017 02:30 PM EST Reads: 2,640
The 20th International Cloud Expo has announced that its Call for Papers is open. Cloud Expo, to be held June 6-8, 2017, at the Javits Center in New York City, brings together Cloud Computing, Big Data, Internet of Things, DevOps, Containers, Microservices and WebRTC to one location. With cloud computing driving a higher percentage of enterprise IT budgets every year, it becomes increasingly important to plant your flag in this fast-expanding business opportunity. Submit your speaking proposal ...
Jan. 22, 2017 02:00 PM EST Reads: 5,294
Thanks to Docker, it becomes very easy to leverage containers to build, ship, and run any Linux application on any kind of infrastructure. Docker is particularly helpful for microservice architectures because their successful implementation relies on a fast, efficient deployment mechanism – which is precisely one of the features of Docker. Microservice architectures are therefore becoming more popular, and are increasingly seen as an interesting option even for smaller projects, instead of being...
Jan. 22, 2017 12:15 PM EST Reads: 2,638
@DevOpsSummit taking place June 6-8, 2017 at Javits Center, New York City, is co-located with the 20th International Cloud Expo and will feature technical sessions from a rock star conference faculty and the leading industry players in the world. @DevOpsSummit at Cloud Expo New York Call for Papers is now open.
Jan. 22, 2017 12:00 PM EST Reads: 3,641
DevOps is being widely accepted (if not fully adopted) as essential in enterprise IT. But as Enterprise DevOps gains maturity, expands scope, and increases velocity, the need for data-driven decisions across teams becomes more acute. DevOps teams in any modern business must wrangle the ‘digital exhaust’ from the delivery toolchain, "pervasive" and "cognitive" computing, APIs and services, mobile devices and applications, the Internet of Things, and now even blockchain. In this power panel at @...
Jan. 22, 2017 11:45 AM EST Reads: 2,976
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 ...
Jan. 22, 2017 11:45 AM EST Reads: 6,466
2016 has been an amazing year for Docker and the container industry. We had 3 major releases of Docker engine this year , and tremendous increase in usage. The community has been following along and contributing amazing Docker resources to help you learn and get hands-on experience. Here’s some of the top read and viewed content for the year. Of course releases are always really popular, particularly when they fit requests we had from the community.
Jan. 22, 2017 11:00 AM EST Reads: 1,252
You often hear the two titles of "DevOps" and "Immutable Infrastructure" used independently. In his session at DevOps Summit, John Willis, Technical Evangelist for Docker, covered the union between the two topics and why this is important. He provided an overview of Immutable Infrastructure then showed how an Immutable Continuous Delivery pipeline can be applied as a best practice for "DevOps." He ended the session with some interesting case study examples.
Jan. 22, 2017 10:30 AM EST Reads: 3,285
Buzzword alert: Microservices and IoT at a DevOps conference? What could possibly go wrong? In this Power Panel at DevOps Summit, moderated by Jason Bloomberg, the leading expert on architecting agility for the enterprise and president of Intellyx, panelists peeled away the buzz and discuss the important architectural principles behind implementing IoT solutions for the enterprise. As remote IoT devices and sensors become increasingly intelligent, they become part of our distributed cloud enviro...
Jan. 22, 2017 08:30 AM EST Reads: 5,017
In 2014, Amazon announced a new form of compute called Lambda. We didn't know it at the time, but this represented a fundamental shift in what we expect from cloud computing. Now, all of the major cloud computing vendors want to take part in this disruptive technology. In his session at 20th Cloud Expo, John Jelinek IV, a web developer at Linux Academy, will discuss why major players like AWS, Microsoft Azure, IBM Bluemix, and Google Cloud Platform are all trying to sidestep VMs and containers...
Jan. 22, 2017 08:30 AM EST Reads: 991
DevOps tends to focus on the relationship between Dev and Ops, putting an emphasis on the ops and application infrastructure. But that’s changing with microservices architectures. In her session at DevOps Summit, Lori MacVittie, Evangelist for F5 Networks, will focus on how microservices are changing the underlying architectures needed to scale, secure and deliver applications based on highly distributed (micro) services and why that means an expansion into “the network” for DevOps.
Jan. 22, 2017 06:30 AM EST Reads: 5,620