Use system orchestration to get the benefits of automation
While implementing DevOps, companies must be aware of creating new potential silos as they implement domain-specific deploys. A central coordination service is needed that provides end-to-end visibility of the way the different aspects of the network system is deployed while allowing each domain to manage itself autonomously to reduce management complexity and functional duplication. Multi-domain system orchestration enables services to be managed and manipulated from end-to-end, from a central point and at a high level of abstraction.
Accommodate legacy systems where necessary
Large enterprises, particularly in sensitive sectors such as financial services and healthcare, for example, often have complex legacy infrastructure constraints.
Implementing DevOps on one business practice might impact another application, or have legal ramifications. These organisations must think about new ways to incorporate the DevOps mentality into their standard processes.
Enterprises like these must be pragmatic about legacy systems: heterogeneity is a fact of network life. Such organisations might consider what Gartner refers to as 'bimodal IT' - balancing the need to maintain legacy processes in some areas, while automating where possible to achieve both IT agility and stability.
Adopt a DevOps toolkit and then do it themselves
The DevOps toolkit that an enterprise chooses is the enabler to develop new, virtualized services quickly, customize them and differentiate them. Rather than outsourcing to big integrators to the extent that they might find themselves dependent on them, enterprises must choose a toolkit that empowers them to take control after having someone take them through the initial start up and training. Ideally, the toolkit must allow enterprises to either build services themselves or utilise a professional services team to do it - but they should not be constrained by either approach.
In today's fast evolving business environment the 'old way' of doing business is unsustainable. A DevOps software offering choice, openness, empowerment, and self-service must be combined with a development approach that combines pragmatism with strategic thinking. This model will allow enterprises to integrate their product development, IT and operations to create an interconnected ecosystem that reduces the time required to offer new services and quickly adapt to changing market needs.
Sign up for Computerworld eNewsletters.