Welcome!

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

Related Topics: @DevOpsSummit, Java IoT, Linux Containers, Agile Computing, @CloudExpo, @DXWorldExpo, SDN Journal

@DevOpsSummit: Blog Post

The New Requirements for App Delivery – @DevOpsSummit Story [#DevOps]

The new world is an application world, and it's not just having them on the Internet that counts

Application delivery, as defined as its own little corner of the network industry, has been fairly focused on assuring the performance, security and availability of applications since its inception back around 2003. Oh, the ways in which those three core tenets have been supported by application delivery controllers has evolved during that time, but always the focus was on the goal of making apps fast, secure and available.

But that was then, and this is next. The new world is an application world, and it's not just having them on the Internet that counts. Applications - whether mobile or web, consumer or employee - are what enable and grow business today. The app is a requirement, a competitive differentiator, the keystone of an ecosystem around which businesses will rise and fall.

mcadam-alignAnd while it is certainly still the case that apps should be fast, secure and available, it's increasingly becoming true that they must also get to market faster, scale faster and more efficiently, and increase productivity. As our CEO John McAdam noted in his keynote at Agility 2014, IT and the business must work together to deliver applications while meeting - for perhaps the first time in years - objectives that are aligning. Which may mean being delivered on-premise or off, in a cloud or from a traditional data center. They may be native mobile or web apps and they might just be SaaS. The goal is lowering IT operational costs and increasing productivity all while improving time to market.

All this variety means "the network" must evolve. It must take the next step toward supporting apps everywhere that interact with users anywhere. And since a significant portion of "the network" lies at layers 4-7 in application services, that means app delivery must continue to evolve.

App delivery must support the opportunity inherent in the new application world by adapting and adopting the paradigms and precepts  behind cloud, devops, SDN, and evolving security models in order to meet the goals of fast, secure and available applications provisioned in minutes instead of months and with reduced operational costs.

new reqs for app delivery

As our EVP Manny Rivelo noted in his keynote, it's more than just changing features and functionality and adding services this time. This time it's changing the very foundations of how application delivery solutions are architected, managed, integrated and even ultimately where they reside. App delivery "next" has to address deployment of its services, moving from months to minutes, from manual to programmable. Its network infrastructure model must support multi-tenancy and move from hardware products to software-defined platforms. Its basic availability and operating modes must change from HA pairs and overprovisioning to elasticity and enabling hybrid cloud deployments. And it must decouple from the network access and app protection, moving away from IP to ID-based security models.

The new app delivery requirements must do more than just deliver apps. It must enable the application world in which "application" is synonymous with "opportunity."

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.
The explosion of new web/cloud/IoT-based applications and the data they generate are transforming our world right before our eyes. In this rush to adopt these new technologies, organizations are often ignoring fundamental questions concerning who owns the data and failing to ask for permission to conduct invasive surveillance of their customers. Organizations that are not transparent about how their systems gather data telemetry without offering shared data ownership risk product rejection, regulatory scrutiny and increasing consumer lack of trust in technology in general.