Now that you're (ideally) operating in a cloud-first
world, a DevOps operating model becomes the norm.
With this transition comes a frequent assumption that implementing DevOps
"correctly" means giving developers the ability to manage the full lifecycle of
their applications and the platform services that support them.
While there will certainly be specific use cases where this "full stack, full
lifecycle" approach to DevOps makes sense, most enterprises will benefit
from having a central team that handles the undifferentiated heavy lifting of
configuring and integrating AWS platform services on the developers' behalf.
This is especially true for large enterprises with a varied application portfolio.
This approach ensures the platform services supporting your applications
adhere to corporate standards for architecture, operational excellence, security,
and compliance—as well as financial controls—without burdening developers
with these platform governance concerns.
Implementing a core team for these platform services frees development
teams to focus on maximizing the business impact—and value—of their
applications. Developers can then migrate and optimize their applications
faster, using standardized, self-service enterprise capabilities.
This core team within your company becomes your "Cloud
Enablement Engine."
8
Build your Cloud Enablement Engine
19
