Cloud Operating Models
Cloud Operating Models
Embedded Files
Consuming cloud services means that costs are now highly variable and invoiced after consumption. This is a completely new experience for most roles within the organization. There are several different operating models that organizations commonly use in the cloud, each with its own set of advantages and disadvantages.
Centralized
Centralized
Central Engineering team will perform Cloud Actions
Cost is clearly accounted for when all cloud actions are run through a centralized team.
Change may be slower if many teams have requests all at one time.
Limited innovation for roles outside of the central engineering team.
Shared Platform
Shared Platform
Centralized team offers a platform. The platform provides a layer of abstraction from the native cloud resources.
Through this centralized tooling/APIs, teams across the organization will be able to utilize the cloud-based features and options made available by the platform.
As engineers, you have the freedom to create within a given set of parameters.
Fully Distributed
Fully Distributed
In this model, all teams have direct access to the cloud. Each team makes autonomous decisions and is expected to adhere to general guidelines regarding cloud usage.
As an engineer, you have direct access to the cloud with the expectation to 'be good.' However, this can result in a lack of accountability, duplication of efforts, and overspending.
Cloud Center of Excellence
Cloud Center of Excellence
In a Fully Distributed model, there may be a Cloud Center of Excellence (CCoE) that defines which cloud services teams can use, sets tagging policies, and governs access and permissions. Additionally, some organizations may operate in multiple models simultaneously.
Page updated
Google Sites
Report abuse