Containers Expo Blog Authors: Pat Romanski, Zakia Bouachraoui, Elizabeth White, Liz McMillan, Yeshim Deniz

Related Topics: Containers Expo Blog, @CloudExpo

Containers Expo Blog: Blog Feed Post

The Devil Is in the Details

Or more apropos, it’s in the complex and intimate relationship between applications and their infrastructure

Virtualization Magazine on Ulitzer

Or more apropos, it’s in the complex and intimate relationship between applications and their infrastructure.


What’s the difference between a highly virtualized corporate data center and a cloud computing environment? There are probably many, but the most important distinction – and the one that earns the latter a “cloud computing” tag – is certainly that the former lacks a comprehensive orchestration system and was likely not architected using a rapid, infrastructure inclusive, scalability strategy.

Mitch Garnaat, “The Elastician”, recently managed to sum up what should be every modern data center’s motto in a single, six word tweet: “Scale is not just about servers.” In fact, I am hereby dubbing this “Garnaat’s Theorem”, as this fundamental data center truth has been established and proven more times than some of us would care to remember.

Mitch could not be more right. Scale is not just about servers, and for corporate data centers and cloud computing providers looking to realize the benefits of rapid elasticity and on-demand provisioning scale simply must be one of the foundational premises upon which a dynamic data center is built. And that includes the infrastructure.


image It’s a fine thing to be able to replicate and deploy many instances of an application to achieve higher capacity, better performance, and fault tolerance. But if the underlying infrastructure is not also prepared to handle the higher volume of traffic and requests, such a strategy will ultimately fail. Large scale data centers already know this; the network and application network infrastructure over which high volume web applications are delivered must also scale to meet application demand or risk becoming the bottleneck and cause of poor performance.


Bandwidth seems a no brainer, after all we’re running data centers built on 10Gbps backbones today. But individual NICs on servers and ports on switches and other network infrastructure solutions are often still only capable of handling 1Gbps. A very large server (think 8, 16, or more cores) may have multiple NICs but each may be only 1Gbps. Scaling bandwidth, then, becomes a matter of architecting the network such that more bandwidth is available to the server. Teaming of NICs is often used as a means to combine multiple network connections into a “virtual” network connection that can handle many more Gbps of traffic. But simply teaming NICs or deploying a vSwitch on the server will only help distribute application responses, because the software responsible for binding those NICs together only has control over the server-side traffic. To scale network traffic bidirectionally it’s necessary to also configure the network solution(s) on the other end of that link – might be a switch, might be a load balancing device, etc… – to also bind together the appropriate network connections to form a single, logical link between the server and the network device.

Consider what that means in relation to scalability. Port densities on switches and application network solutions have increased, yes, but in organizations other than the largest it is likely many of those devices do not have more than 48 ports available, i.e. there are only 48 network connections available for connection servers. If each large server is teaming four NICs together, that means four ports on the network infrastructure should also be “teamed” together, which reduces the number of servers able to be physically connected to that switch to 12. If the data center has more than 12 “servers” then it’s likely that additional network infrastructure components will be necessary. More NICs teamed together means fewer servers physically connected, which can dramatically change the physical (and logical) network and application network infrastructure architecture.


Most organizations have other network, security, and application network infrastructure that architecturally sits “in front of” the applications. Each of these components must be capable of scaling in tandem with the servers and applications being scaled. If it is expected that an application can scale from 10,000 concurrent users to 50,000 concurrent users, so must the infrastructure be capable of scaling. Some solutions, such as IPS and IDS in the security world – and even many WAFs (Web Application Firewalls) - are often configured to transparently monitor and subsequently act on incoming and outgoing responses. These solutions require ports on infrastructure switching solutions, and thus if it is necessary to scale them to support higher volumes of traffic they, too, will require additional ports on infrastructure switching solutions whether because network connections are aggregated to provide the bandwidth necessary and mitigate bandwidth limiting bottlenecks or because multiple instances (physical or virtual) of the solution are being deployed. Every solution needs its own network connection, caution-loadlimitafter all.


Speaking of network connections needed by infrastructure solutions, “data center scalability” also requires careful consideration of the management network. Most infrastructure solutions utilize separate management ports as a means to enable out-of-band management. This mitigates the risk of being unable to access and manage a given infrastructure component in the face of overwhelming traffic, such as a DDoS scenario or failed network connection. Whether this is accomplished via a physically or logically separate network is a matter of budget and design, but in either case requires careful attention to the architecture of the data center to allow both the “work” network and the “management” network to scale along with the application.

This also should trigger concern or at least a line item on the scalability to-do list to inquire as to the scalability of network management systems (NMS) used to manage these applications and its infrastructure. More infrastructure, more complex architectures, more applications and servers will certainly add stressors on the NMS that may not have been present before. It may be necessary to scale that solution, as well, which impacts the network and application network infrastructure as well as the applications, depending on the solution used.


When folks start getting excited about the idea of Virtual Network Appliances (VNAs) as a means to achieve some of the scalability challenges I’ve noted above, they are thinking about scalability of infrastructure (which is good) but forget that the VNA is going to incur the same scalability challenges that a virtualized application would incur (which is not so good). The “Spin Strategy”, i.e. spin up a new instance of X to address increasing demand, is not a strategy at all, it’s a tactical measure to addressing a specific task within what should be an architectural strategy to scalability. We’ve barely touched on the challenges associated with infrastructure scalability in this post; there are many other factors to consider. What should be clear, however, is that Garnaat’s Theorem holds true: scale is not just about servers. There are many, many more pieces of the architectural puzzle that go into scalability and it behooves data center architects to consider the impact of scaling approaches – up, out, virtual, physical – before jumping into an implementation.

This isn’t the first time I’ve touched upon this subject, but it’s a concept that needs to be reiterated – especially with so many pundits and analysts looking for the next big virtualization wave to crash onto the infrastructure beachhead. I’m here to tell you, though, that the devil is in the details. The architectural details.

Read the original blog entry...

More Stories By Lori MacVittie

Lori MacVittie is responsible for education and evangelism of application services available across F5’s entire product suite. Her role includes authorship of technical materials and participation in a number of community-based forums and industry standards organizations, among other efforts. MacVittie has extensive programming experience as an application architect, as well as network and systems development and administration expertise. Prior to joining F5, MacVittie was an award-winning Senior Technology Editor at Network Computing Magazine, where she conducted product research and evaluation focused on integration with application and network architectures, and authored articles on a variety of topics aimed at IT professionals. Her most recent area of focus included SOA-related products and architectures. She holds a B.S. in Information and Computing Science from the University of Wisconsin at Green Bay, and an M.S. in Computer Science from Nova Southeastern University.

IoT & Smart Cities Stories
Nicolas Fierro is CEO of MIMIR Blockchain Solutions. He is a programmer, technologist, and operations dev who has worked with Ethereum and blockchain since 2014. His knowledge in blockchain dates to when he performed dev ops services to the Ethereum Foundation as one the privileged few developers to work with the original core team in Switzerland.
Andrew Keys is Co-Founder of ConsenSys Enterprise. He comes to ConsenSys Enterprise with capital markets, technology and entrepreneurial experience. Previously, he worked for UBS investment bank in equities analysis. Later, he was responsible for the creation and distribution of life settlement products to hedge funds and investment banks. After, he co-founded a revenue cycle management company where he learned about Bitcoin and eventually Ethereal. Andrew's role at ConsenSys Enterprise is a mul...
René Bostic is the Technical VP of the IBM Cloud Unit in North America. Enjoying her career with IBM during the modern millennial technological era, she is an expert in cloud computing, DevOps and emerging cloud technologies such as Blockchain. Her strengths and core competencies include a proven record of accomplishments in consensus building at all levels to assess, plan, and implement enterprise and cloud computing solutions. René is a member of the Society of Women Engineers (SWE) and a m...
If a machine can invent, does this mean the end of the patent system as we know it? The patent system, both in the US and Europe, allows companies to protect their inventions and helps foster innovation. However, Artificial Intelligence (AI) could be set to disrupt the patent system as we know it. This talk will examine how AI may change the patent landscape in the years to come. Furthermore, ways in which companies can best protect their AI related inventions will be examined from both a US and...
In his general session at 19th Cloud Expo, Manish Dixit, VP of Product and Engineering at Dice, discussed how Dice leverages data insights and tools to help both tech professionals and recruiters better understand how skills relate to each other and which skills are in high demand using interactive visualizations and salary indicator tools to maximize earning potential. Manish Dixit is VP of Product and Engineering at Dice. As the leader of the Product, Engineering and Data Sciences team at D...
Bill Schmarzo, Tech Chair of "Big Data | Analytics" of upcoming CloudEXPO | DXWorldEXPO New York (November 12-13, 2018, New York City) today announced the outline and schedule of the track. "The track has been designed in experience/degree order," said Schmarzo. "So, that folks who attend the entire track can leave the conference with some of the skills necessary to get their work done when they get back to their offices. It actually ties back to some work that I'm doing at the University of San...
When talking IoT we often focus on the devices, the sensors, the hardware itself. The new smart appliances, the new smart or self-driving cars (which are amalgamations of many ‘things'). When we are looking at the world of IoT, we should take a step back, look at the big picture. What value are these devices providing. IoT is not about the devices, its about the data consumed and generated. The devices are tools, mechanisms, conduits. This paper discusses the considerations when dealing with the...
Bill Schmarzo, author of "Big Data: Understanding How Data Powers Big Business" and "Big Data MBA: Driving Business Strategies with Data Science," is responsible for setting the strategy and defining the Big Data service offerings and capabilities for EMC Global Services Big Data Practice. As the CTO for the Big Data Practice, he is responsible for working with organizations to help them identify where and how to start their big data journeys. He's written several white papers, is an avid blogge...
Dynatrace is an application performance management software company with products for the information technology departments and digital business owners of medium and large businesses. Building the Future of Monitoring with Artificial Intelligence. Today we can collect lots and lots of performance data. We build beautiful dashboards and even have fancy query languages to access and transform the data. Still performance data is a secret language only a couple of people understand. The more busine...
Enterprises have taken advantage of IoT to achieve important revenue and cost advantages. What is less apparent is how incumbent enterprises operating at scale have, following success with IoT, built analytic, operations management and software development capabilities - ranging from autonomous vehicles to manageable robotics installations. They have embraced these capabilities as if they were Silicon Valley startups.