Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Looking Into E-DevOps (Enterprise DevOps)

DZone's Guide to

Looking Into E-DevOps (Enterprise DevOps)

Take a look into E-DevOps and look at some of the key framework principles that one should consider for successful DevOps at the enterprise level.

· DevOps Zone ·
Free Resource

Do you need to strengthen the security of the mobile apps you build? Discover more than 50 secure mobile development coding practices to make your apps more secure.

DevOps is quickly evolving as foundational capability to get business and IT agility. While most companies are able to adopt DevOps automation (CI/CD pipeline) at the team or system level, they are not able to scale it at an enterprise level.

Like the Agile practice of Scrum needs to be built over with enterprise frameworks like SAFe, Scrum of Scrum, LeSS, DaD, etc., E-DevOps also needs to be built on certain key framework principles.

Below are some of the key framework principles that one should consider for successful DevOps at the enterprise level:

Image title

CI/CD Pipeline

An organization should define a standard continuous delivery (SCD) procedure per strategic technology. In addition to defining an SCD pipeline per technology, some addition points to consider are:

  • Single source control and repository
  • Single service/release orchestration solution

Platform

There are several models for managing platforms for a CI/CD pipeline. As with any model, it’s a trade-off between flexibility, standardization, support model, and cost factor.

A cloud model would be using the existing CD-as-a-service by cloud providers. Central hosting can be on-premise or on the cloud but is managed by the client. Team setup is where each team creates and maintain its pipeline. The base image of the pipeline can be managed by centrally. Containerization is just an extension of this model with a different deployment strategy.

Image title

Tooling Support

Support for CI/CD tooling at least the SCD (baselined) should be centrally controlled. The tool's lifecycle management (LCM) support with guidelines and coaching of the team for adoption can be defined on the model.

Image title

CI/CD Maturity

There are several models for looking at CI/CD maturity. It's good metrics to measure depth and breadth per system/technology so that adoption can be tracked. We see integration of security, risk, and other operational aspects as part of the pipeline.

Image title

While we will continue to see DevOps itself evolve into new mature avatars like DevSecOps, ChatOps, BotOps, NoOps, etc., it is important that foundation enterprise setup is done right.

Check out tips for blazing the way from agile to DevSecOps with security built into your mobile app toolchain.

Topics:
devops ,enterprise devops ,scaling devops

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}