A Cisco-Insieme primer: What is application-centric infrastructure2013-11-052013-11-05https://www.plexxi.com/wp-content/uploads/2018/04/plexxi-logo-rgb.pngPlexxihttps://www.plexxi.com/wp-content/uploads/2018/04/plexxi-logo-rgb.png200px200px
With the launch of Cisco’s software-defined networking startup Insieme expected tomorrow, our industry is about to hear a lot about “application-centric” everything. So what does “application-centric infrastructure” mean?
First, some basics: Networking is about connecting computing devices and systems so they can share data. Networking infrastructures are built with a combination of hardware such as gateways, routers, and switches that manage the movement of the data as well as software applications that enable you to do things like access the Internet and send email.
As you could probably guess, application-centric infrastructure is a type of networking that is based on the application. In an application-centric network, the network administrator manages a system for a specific application rather than managing individual servers and routers like they did in the past.
In application-centric networking, success is determined by the end user’s experience with an application. So the best metric to measure that success might be something like application responsiveness or uptime. This requires a different level of instrumentation within the supporting infrastructure. Administrative entry points to the network need to include more than just traditional networking information. There are several questions you need to ask: Can you see how applications are talking across your network? For distributed applications, do you have a view of which components are where? Can you see how data is flowing between them?
In application-centric networking, the problem to be solved is not specific to a router or switch. It is more tied to the application and the IT systems that support it as a whole. This implies a level of integration with surrounding infrastructure beginning with the application.
In application-centric networking, troubleshooting does not mean logging into discrete devices and examining networking state information. If a web application is not performing, you start with the web application. The fact that relevant state information might exist within a router, switch, or even a webserver is secondary. You want to gather intelligence on the application itself. That data needs to be collected and correlated. And you aren’t done until the application is up and running as it should.
“Application-centric infrastructure” is more than just a marketing term. It is more than rebranding the same tired solutions in a new way. It is more than a new fad designed to sell old gear. Or at least it ought to be.
Having seen bits and pieces of what Cisco is planning with Insieme, I like the vision. I like that they are putting applications where they ought to have been all along: at the start of the process. I like that our industry is starting to move away from a reactive networking approach to a more proactive infrastructure that plans for — rather than responds to — application demands.
In fact, I like it so much, I joined a company that has been working towards this vision for the past three years.