Welcome!

Microservices Expo Authors: Flint Brenton, Liz McMillan, Elizabeth White, Charles Araujo, Ed Witkovic

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.

app-network

LAYER 2-3

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.

LAYER 4-7

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.


LET THEM USE THE NETWORK


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.


EVOLUTION ISN’T JUST FOR TECHNOLOGY


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.

@MicroservicesExpo Stories
Don’t go chasing waterfall … development, that is. According to a recent post by Madison Moore on Medium featuring insights from several software delivery industry leaders, waterfall is – while still popular – not the best way to win in the marketplace. With methodologies like Agile, DevOps and Continuous Delivery becoming ever more prominent over the past 15 years or so, waterfall is old news. Or, is it? Moore cites a recent study by Gartner: “According to Gartner’s IT Key Metrics Data report, ...
Agile has finally jumped the technology shark, expanding outside the software world. Enterprises are now increasingly adopting Agile practices across their organizations in order to successfully navigate the disruptive waters that threaten to drown them. In our quest for establishing change as a core competency in our organizations, this business-centric notion of Agile is an essential component of Agile Digital Transformation. In the years since the publication of the Agile Manifesto, the conn...
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...
The next XaaS is CICDaaS. Why? Because CICD saves developers a huge amount of time. CD is an especially great option for projects that require multiple and frequent contributions to be integrated. But… securing CICD best practices is an emerging, essential, yet little understood practice for DevOps teams and their Cloud Service Providers. The only way to get CICD to work in a highly secure environment takes collaboration, patience and persistence. Building CICD in the cloud requires rigorous ar...
"This all sounds great. But it's just not realistic." This is what a group of five senior IT executives told me during a workshop I held not long ago. We were working through an exercise on the organizational characteristics necessary to successfully execute a digital transformation, and the group was doing their ‘readout.' The executives loved everything we discussed and agreed that if such an environment existed, it would make transformation much easier. They just didn't believe it was reali...
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...
"Opsani helps the enterprise adopt containers, help them move their infrastructure into this modern world of DevOps, accelerate the delivery of new features into production, and really get them going on the container path," explained Ross Schibler, CEO of Opsani, and Peter Nickolov, CTO of Opsani, in this SYS-CON.tv interview at DevOps Summit at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
The purpose of this article is draw attention to key SaaS services that are commonly overlooked during contact signing that are essential to ensuring they meet the expectations and requirements of the organization and provide guidance and recommendations for process and controls necessary for achieving quality SaaS contractual agreements.
What's the role of an IT self-service portal when you get to continuous delivery and Infrastructure as Code? This general session showed how to create the continuous delivery culture and eight accelerators for leading the change. Don Demcsak is a DevOps and Cloud Native Modernization Principal for Dell EMC based out of New Jersey. He is a former, long time, Microsoft Most Valuable Professional, specializing in building and architecting Application Delivery Pipelines for hybrid legacy, and cloud ...
The “Digital Era” is forcing us to engage with new methods to build, operate and maintain applications. This transformation also implies an evolution to more and more intelligent applications to better engage with the customers, while creating significant market differentiators. In both cases, the cloud has become a key enabler to embrace this digital revolution. So, moving to the cloud is no longer the question; the new questions are HOW and WHEN. To make this equation even more complex, most ...
CloudEXPO New York 2018, colocated with DXWorldEXPO New York 2018 will be held November 11-13, 2018, in New York City and will bring together Cloud Computing, FinTech and Blockchain, Digital Transformation, Big Data, Internet of Things, DevOps, AI, Machine Learning and WebRTC to one location.
Docker is sweeping across startups and enterprises alike, changing the way we build and ship applications. It's the most prominent and widely known software container platform, and it's particularly useful for eliminating common challenges when collaborating on code (like the "it works on my machine" phenomenon that most devs know all too well). With Docker, you can run and manage apps side-by-side - in isolated containers - resulting in better compute density. It's something that many developer...
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...
"We're developing a software that is based on the cloud environment and we are providing those services to corporations and the general public," explained Seungmin Kim, CEO/CTO of SM Systems Inc., in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
We all know that end users experience the internet primarily with mobile devices. From an app development perspective, we know that successfully responding to the needs of mobile customers depends on rapid DevOps – failing fast, in short, until the right solution evolves in your customers' relationship to your business. Whether you’re decomposing an SOA monolith, or developing a new application cloud natively, it’s not a question of using microservices - not doing so will be a path to eventual ...
Explosive growth in connected devices. Enormous amounts of data for collection and analysis. Critical use of data for split-second decision making and actionable information. All three are factors in making the Internet of Things a reality. Yet, any one factor would have an IT organization pondering its infrastructure strategy. How should your organization enhance its IT framework to enable an Internet of Things implementation? In his session at @ThingsExpo, James Kirkland, Red Hat's Chief Archi...
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 ...
We all know that end users experience the internet primarily with mobile devices. From an app development perspective, we know that successfully responding to the needs of mobile customers depends on rapid DevOps – failing fast, in short, until the right solution evolves in your customers' relationship to your business. Whether you’re decomposing an SOA monolith, or developing a new application cloud natively, it’s not a question of using microservices - not doing so will be a path to eventual ...
We all know that end users experience the Internet primarily with mobile devices. From an app development perspective, we know that successfully responding to the needs of mobile customers depends on rapid DevOps – failing fast, in short, until the right solution evolves in your customers' relationship to your business. Whether you’re decomposing an SOA monolith, or developing a new application cloud natively, it’s not a question of using microservices – not doing so will be a path to eventual b...
The past few years have brought a sea change in the way applications are architected, developed, and consumed—increasing both the complexity of testing and the business impact of software failures. How can software testing professionals keep pace with modern application delivery, given the trends that impact both architectures (cloud, microservices, and APIs) and processes (DevOps, agile, and continuous delivery)? This is where continuous testing comes in. D