DevOps – An OCI perspective 

DevOps is the collaboration of software developers and other technologists to streamline and improve the processes for various stakeholders to build, test, and release software and applications. These improvements are achieved by automating delivery and infrastructure changes.

DevOps is making the leap from code to cloud manageable – with software deployment and Continuous Delivery at speeds never before seen.  For mission critical systems that need to run without interruption, DevOps is a must-have.  Its software development and deployment processes keep pace with the demands of modern, competitive business and the volatility of the market.

DevOps supports Continuous Integration, delivery, testing and monitoring using automated, scalable infrastructure and solutions inspired by agile practices. DevOps also benefits organizations by reducing miscommunication between development and operations and ensuring reliable, predictable, repeatable, infrastructure, while minimizing creation-to-deployment time.

Well . . . at least this is what DevOps promises.

The reality of the above vision remains elusive for most companies as the vision may be clear, while the path remains problematic. So the reality for most companies looks something like this:

DevOps is dispersed among many tools


The current DevOps state for most companies is likely in various stages of effectiveness and value.  Some pockets (different by company) of success likely exist, but success across the entire organization remains elusive for most organizations, because of numerous impediments and the reality that existing legacy applications usually resist change.

OCI takes a different and perhaps unique approach to DevOps.  OCI accepts and frankly embraces the idea that no single DevOps “tool” can or will provide everything needed to make the practices of DevOps fully optimal and relevant across an organization.  Even the various definitions within the broader marketplace of what DevOps actually covers helps illustrate just how illusory the vision of a single “tool” solution remains. 

OCI’s approach is simply to provide visibility and seamless integration points into the various DevOps tools that are currently being used within a company.  This integrated and cohesive view allows organizational DevOps analysis that is not possible with today’s functional, but isolated, DevOps’ tools. 

This integrated and holistic view fully supports the concept of incremental improvement among the people, processes, and technologies of DevOps, enabling the organization to measure and expose the impact of existing inefficiencies, and the subsequent actions organizations can take to rectify the issues this approach helps reveal.  Additionally, it provides flexibility for tool choice, minimizing the impact of migrating to new DevOps tools, while providing a much more comprehensive organizational view into the processes.  

This cohesive, and collaborative architectural approach is pictured below:

future state - from tools to insight

Continuity is not necessarily a revelation, but it is pragmatic and practical – capitalizing on the individual strengths and capabilities of the plethora of DevOps tools already in existence.  Tools that likely can’t and perhaps never will talk to each other to provide a holistic organization view of DevOps. Continuity enables organizations to collectively hear, comprehend, and fully utilize all the tools that talk DevOps.

WebSanity Top Secret