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

Related Topics: Microservices Expo, Agile Computing

Microservices Expo: Blog Feed Post

Differentiating the Application Network from the Network

The network ain't big enough for the both of us

There is a tendency to describe every device on a network as simply “the network” regardless of whether that device is dedicated to security, or application delivery (layer 4-7), or actual network (layer 2-3) functionality. It’s an artifact of aging data center architecture models that there exists an artificial line of demarcation between web and application servers and everything else. We used to depict “everything else” as a cloud, but with the emergence of The Cloud doing so simply complicates discussions even further because the “network” necessary to support a dynamic, on-demand operational model of computing like “cloud” is more complex.

Load balancing and application switching
functionality is no longer a “nice to have”, it’s a “must have” in order to properly abstract applications such that users can remain blissfully ignorant of the inner workings of the cloud. But it’s rarely broken out that way; everything that’s not a server is evidently part of “the network” regardless of where its true demesne within the architecture may lie.

The problem with the “tossed salad” approach of discussing “the network” is that there are very real differences between the network (layer 2-3) and the application network (layer 4-7) that make such a mixing of solutions problematic. Certainly every device on the network is capable of performing some layer 2-3 functions else it could not reside “on the network” in the first place, but that does necessarily mean that every device on the network is focused on providing additional value above and beyond what is necessary to forward packets in the most expedient manner possible.



A network is primarily concerned with the routing of packets from one host to another through a series of connections. It may apply some logic to that routing in order to comply with business goals related to response time or availability, but in general the “network” doesn’t really care whether the application is SAP or SharePoint or a custom application. It only cares about the packets and how best to route them to the next hop. The only time a network really cares about the application is when it needs to decide which packets to forward first when there is limited bandwidth and then it only cares about the application in so far as it can distinguish between SharePoint and SAP so it can make a routing decision.


An application delivery network, or just application network, is less concerned with the routing of individual packets (it does it, but that’s not its primary concern) and is more focused on the entire application stream. It must know what application is being processed because its decisions about how to treat an application stream are almost always derived from a policy that is based on the application. An application network must be intimately familiar with all the particular nuances and quirks of an application and its associated protocols – from layer 4 to layer 7 to the application itself – because much of its value is in being able to provide application specific optimizations, acceleration, and security. The behavior of an SAP application, for example, is much different than that of SharePoint. The usage patterns are different, the interaction between client and server is different, and the very way in which these applications exchange data is different.

What an application network does is provide an overlay of intermediaries (brokers, proxies, whatever you’d like to call them) that essentially mediate between the client and the server and the application and the network. It’s a layer of functionality over the network that understands both sides of the equation – application and network – and uses information from both to make decisions regarding the best way to ensure an application is available, fast, and secure.


Now usually what happens in discussions is that some folks just blithely say “that functionality belongs in the network”. But what most people think of when the term “the network” is used is routing and switching and thus reasonable folks will immediately dismiss the notion of putting X functionality “in the network” because it doesn’t make sense. Web application security, for example, doesn’t belong in a router or switch because those devices are packet-based and generally unaware of the nuances involved with inspecting web application data for SQL injection or XSS attacks. Similarly, load balancing “in the network” is associated with port trunking/link aggregation or assuring availability through the use of two or more ISP links, not application-specific switching and routing.

The use of “the network” as an umbrella term to describe a varied range of functions and responsibilities across the networking stack is as confusing as the use of “the cloud” to refer to the myriad data center architectural models emerging today. The lack of qualification of “the cloud” in discussions causes as much confusion as does the lack of qualification around “the network.” Consider as an example the differences between network acceleration and application acceleration as an incarnation of this particular problem. The two are very different technologies and yet they are often lumped together as just “acceleration” without any care or concern for not only the technological adn-osi-overlaydifferences but the distinct business value each adds.

The reason this is so very frustrating is that as soon as an application network device is described as “in the network” the very people who might benefit most from much of its functionality – developers and application architects – immediately dismiss the solution as something outside their demesne to be relegated to the network operations folks for further exploration. That’s a problem because it means that the application half of an application network is often summarily ignored in favor of the network half of the device because that’s what the network operations team understands and has responsibility for.


The real issue here is that as technology has evolved and resulted in new solutions the terminology we use to describe it has not. Because we continue to use the same terms to describe completely different foci it is nearly impossible to have a meaningful discussion without first coming to an understanding of what we’re talking about. A “session”, after all, has many different meanings depending on what layer of the network stack you are focusing. The lack of qualification wastes time that many people today just don’t have and allows for the manipulation of terminology to the detriment of the end-user/customer.

The “network” is not the “application network” – and vice versa. The benefits, roles, and responsibilities relevant to the delivery of applications are very different at layer 2-3 than they are at layer 4-7. Lumping the two together makes it difficult to fully realize the benefits of the latter because it ends up treated as something it is not because we all have preconceived notions about what a “network” can and cannot do. And it also makes it difficult to leverage layer 2-3 to its fullest potential because either we expect it to be more intelligent about things outside its domain (like application specific functionality) or we treat it like a dumb pipe, neither of which is a good way to view the “network.”

Maybe I’m just being hypercritical (wouldn’t be the first time) but it makes things extremely difficult when two groups of people have a completely different understanding of what “the network” means when we’re trying to talk about an application delivery network. One of the goals of SOA was to provide a terminology such that business stakeholders and IT could start from a common understanding and collaborate on solutions because it was recognized that all of IT and the business owners needed to work together to leverage the concepts of a service-enabled architecture. We need to do the same and not only share terminology with the business but also within the disparate silos that have formed over time in IT.

There is a difference between the “network” and the “application network”. It’s not all that dissimilar from the difference between the tiers in an application architecture. We don’t just say “server” because that could mean “web server”, or “application server” or “database server”. We spell it out. The same is true on the “network” side of the house: there are tiers within the infrastructure architecture that need to be recognized if we’re going to understand how to  fully leverage a dynamic infrastructure and on-demand computing in the future.

So mean what you say, and say what you mean.

Note: Yes, I know that layer 5 & 6 in the OSI model above are “missing” and essentially incorporated into layer 7. That’s because we really don’t use those layers individually, they’re treated as layer 7 in what most folks refer to as the TCP/IP stack or model, which has only the 5 layers. Consider this view of the stack a hybrid of reality and theory.

Follow me on Twitter View Lori's profile on SlideShare AddThis Feed Button Bookmark and Share

Related blogs & articles:

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.

Microservices Articles
When building large, cloud-based applications that operate at a high scale, it’s important to maintain a high availability and resilience to failures. In order to do that, you must be tolerant of failures, even in light of failures in other areas of your application. “Fly two mistakes high” is an old adage in the radio control airplane hobby. It means, fly high enough so that if you make a mistake, you can continue flying with room to still make mistakes. In his session at 18th Cloud Expo, Lee A...
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...
Lori MacVittie is a subject matter expert on emerging technology responsible for outbound evangelism across F5's entire product suite. MacVittie has extensive development and technical architecture experience in both high-tech and enterprise organizations, in addition to network and systems administration expertise. Prior to joining F5, MacVittie was an award-winning technology editor at Network Computing Magazine where she evaluated and tested application-focused technologies including app secu...
Containers and Kubernetes allow for code portability across on-premise VMs, bare metal, or multiple cloud provider environments. Yet, despite this portability promise, developers may include configuration and application definitions that constrain or even eliminate application portability. In this session we'll describe best practices for "configuration as code" in a Kubernetes environment. We will demonstrate how a properly constructed containerized app can be deployed to both Amazon and Azure ...
Modern software design has fundamentally changed how we manage applications, causing many to turn to containers as the new virtual machine for resource management. As container adoption grows beyond stateless applications to stateful workloads, the need for persistent storage is foundational - something customers routinely cite as a top pain point. In his session at @DevOpsSummit at 21st Cloud Expo, Bill Borsari, Head of Systems Engineering at Datera, explored how organizations can reap the bene...
Using new techniques of information modeling, indexing, and processing, new cloud-based systems can support cloud-based workloads previously not possible for high-throughput insurance, banking, and case-based applications. In his session at 18th Cloud Expo, John Newton, CTO, Founder and Chairman of Alfresco, described how to scale cloud-based content management repositories to store, manage, and retrieve billions of documents and related information with fast and linear scalability. He addresse...
The now mainstream platform changes stemming from the first Internet boom brought many changes but didn’t really change the basic relationship between servers and the applications running on them. In fact, that was sort of the point. In his session at 18th Cloud Expo, Gordon Haff, senior cloud strategy marketing and evangelism manager at Red Hat, will discuss how today’s workloads require a new model and a new platform for development and execution. The platform must handle a wide range of rec...
SYS-CON Events announced today that DatacenterDynamics has been named “Media 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. DatacenterDynamics is a brand of DCD Group, a global B2B media and publishing company that develops products to help senior professionals in the world's most ICT dependent organizations make risk-based infrastructure and capacity decisions.
Discussions of cloud computing have evolved in recent years from a focus on specific types of cloud, to a world of hybrid cloud, and to a world dominated by the APIs that make today's multi-cloud environments and hybrid clouds possible. In this Power Panel at 17th Cloud Expo, moderated by Conference Chair Roger Strukhoff, panelists addressed the importance of customers being able to use the specific technologies they need, through environments and ecosystems that expose their APIs to make true ...
In his keynote at 19th Cloud Expo, Sheng Liang, co-founder and CEO of Rancher Labs, discussed the technological advances and new business opportunities created by the rapid adoption of containers. With the success of Amazon Web Services (AWS) and various open source technologies used to build private clouds, cloud computing has become an essential component of IT strategy. However, users continue to face challenges in implementing clouds, as older technologies evolve and newer ones like Docker c...