The application-centric cloud development model becomes a devops approach to managing applications. Traditional cultural differences between developers and operations are very pronounced in the current information technology environments, but devops brings forth a blended approach to moving applications and a much quicker and more agile approach to the application-centric cloud.
Devops also makes both sides responsible for the success of the application. It's not only true for an application cloud, but also for the third platform that IDC calls the new environment, or the bifurcated platform, as Gartner calls it. The reason for the new model is that one cannot wait for the cycle times that were created by the old model to facilitate the service level agreements that most companies need to be competitive.
In the new model, developers can develop the code or application and can deploy them in production without having another group involved in the process. That's why the term "developer operations" evolved. The applications deployed can be updated extremely quickly because there is no need for anything other than quality standards that are higher than the standards in the postmodern dev ops environment.
Operations take on a whole new role in this environment as well, ensuring quality and administering the system so that the deployed applications are seamless and productive. Change management still resides with operations, but the operations group must work very closely with developers as they move their code to production. They also have to be totally cognizant of the impact of changes and ensure that the developers are testing in a devops environment well enough to ensure success. The dependencies of composable applications are resolved during development, which saves operations from having to solve problems when an application moves to development operations.
That is why platforms such as OpenShift or Cloud Foundry become critical in the framework that is put in for devops to be consistent with all new languages, databases, and tools. Since not everything is going to move to an application-centric cloud immediately, the operations group and developers have to continue working in the current structure, with the application-centric cloud being an overlay to the current environment. Clearly, this will save the operations group a significant amount of time but, again, you need to have a bifurcation of the group so that devops can flourish.
In both environments, it's important to manage problems within a critical situation group that deals with issues of availability and application SLAs. Problem management will never go away in any model. Even though some articles promise nirvana from this model, getting there will be evolutionary, not revolutionary.
This model enables facile deployment and shared responsibility, not responsibility for one group over the other. When working with financial corporations, clearly, executives must deal with a cultural divide. The lines were drawn a long time ago, and the blending of groups requires the reassignment of people into each group so they can learn what the other group does.
Also, when doing agile development as part of a multidisciplinary operations team, the developers, analysts, and businesspeople take this to a whole new level. Lately, I have seen many companies talking about agile and forcing it into a model that fits the old IT. Most companies believe this will sustain them in the future
In the new environment, I have seen open source products like Cloud Forms, Puppet, and Chef used to manage the environment. As previously stated, the tools are not the issue; the mindset needs to change to a share all environment where success comes from rapid application development and deployment. This would enable system administrators and developers to move to a new level of application deployment. Each group will bring its strengths and weaknesses to the new infrastructure, and this will enable a world of application centricity to become a reality.
This article is published as part of the IDG Contributor Network. Want to Join?