Welcome!

@DevOpsSummit Authors: Liz McMillan, Yeshim Deniz, Zakia Bouachraoui, Pat Romanski, Elizabeth White

Related Topics: Containers Expo Blog, Java IoT, Microservices Expo, Linux Containers, @CloudExpo, SDN Journal, @DevOpsSummit

Containers Expo Blog: Blog Feed Post

Avoiding Network Taxes to Improve App Performance

Consumers are increasingly performance-sensitive, which means every microsecond counts

In the five seconds it takes you to read this, 60% of your visitors just abandoned your site. Another 20% were gone before you even hit the first comma, and 30% of all them are purchasing from one of your competitors.  That's what Limelight Networks "State of the User Experience" says, which pretty much falls in line with every other survey of consumers. They are, on the whole, impatient and unwilling to suffer poor performance when there is a veritable cornucopia of choices available out there on the Internet.

In an application world, apps equal opportunity. But that opportunity is the double-edge sword of Damocles, just as able to offer opportunity to your competitors as it is you.

Application performance has always been critical. So critical, in fact, that entire markets have cropped up with solutions to address the application and network problems that cause poor performance.

userex-bad

Ironically, many of them today may contribute as much to the problem as they do resolve it.

Most web performance optimization (WPO) or front-end optimization (FEO) solutions are pain point products. That means that when a pain point - like web application performance - becomes problematic enough for the business to notice, a solution is quickly acquired and deployed.

And thus begins the conga line of products designed to improve application delivery.

Each addition to the line introduces delay between the consumer and the application. Not because the products are slow or perform poorly, but because there are absolute minimums in terms of the time it takes to open and close TCP sockets and transmit packets over a wire. You can't eliminate it unless you eliminate the solution.

Such an architecture might not be problematic if it was just one or two services, but enterprises typically end up with a significant number line of devices in the critical data path between the consumer and the application.

conga line

Figure 1: Traditional conga-line deployment of application services

Each of these incurs a certain amount of latency necessarily due to network and protocol requirements and contributes to the responsiveness (or lack thereof) of applications. It's a network and protocol tax on each and every service that can't be avoided in this architectural model.

This is where a service platform can help. In addition to its strategic advantages, the platform approach to delivering application services through F5 Synthesis has positive performance implications, as well. When one platform can support the services you need to improve performance and enhance security, you can eliminate all the latency incurred by deploying those same services on multiple, disparate systems.

platform approach

Figure 2: Modern, platform deployment of application services.

By building application services atop a common, high performance service platform, F5 can deliver a broad set of application services without incurring the network and connection taxes required. This eliminates many microseconds (or more, depending on the network topology and conditions) from the consumer response time, meaning applications are delivered faster and consumers don't ditch you for someone else.

A platform approach to application services has many advantages. Eliminating the network and protocol taxes required by traditional service deployment models is one them.

F5 Synthesis High Performance Service Fabric is built atop such a platform, and with the broadest set of application services available on a single platform, you can turn your application service infrastructure into a competitive advantage.

For more information on F5 Synthesis:

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.

@DevOpsSummit Stories
With more than 30 Kubernetes solutions in the marketplace, it's tempting to think Kubernetes and the vendor ecosystem has solved the problem of operationalizing containers at scale or of automatically managing the elasticity of the underlying infrastructure that these solutions need to be truly scalable. Far from it. There are at least six major pain points that companies experience when they try to deploy and run Kubernetes in their complex environments. In this presentation, the speaker will detail these pain points and explain how cloud can address them.
While DevOps most critically and famously fosters collaboration, communication, and integration through cultural change, culture is more of an output than an input. In order to actively drive cultural evolution, organizations must make substantial organizational and process changes, and adopt new technologies, to encourage a DevOps culture. Moderated by Andi Mann, panelists discussed how to balance these three pillars of DevOps, where to focus attention (and resources), where organizations might slip up with the wrong focus, how to manage change and risk in all three areas, what is possible and what is not, where to start, and especially how new structures, processes, and technologies can help drive a new DevOps culture.
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 Atchison, Principal Cloud Architect and Advocate at New Relic, discussed how this same philosophy can be applied to highly scaled applications, and can dramatically increase your resilience to failure.
As Cybric's Chief Technology Officer, Mike D. Kail is responsible for the strategic vision and technical direction of the platform. Prior to founding Cybric, Mike was Yahoo's CIO and SVP of Infrastructure, where he led the IT and Data Center functions for the company. He has more than 24 years of IT Operations experience with a focus on highly-scalable architectures.
CI/CD is conceptually straightforward, yet often technically intricate to implement since it requires time and opportunities to develop intimate understanding on not only DevOps processes and operations, but likely product integrations with multiple platforms. This session intends to bridge the gap by offering an intense learning experience while witnessing the processes and operations to build from zero to a simple, yet functional CI/CD pipeline integrated with Jenkins, Github, Docker and Azure.