Cloud Deployment Models
A cloud deployment model outlines the basic architecture and usage parameters of the enterprise cloud. In a broad sense, cloud deployment models fall into three categories: public, private and hybrid clouds. Beyond that, there is a wide set of options that help optimize an individual cloud for its targeted use cases.
Key considerations when crafting a cloud deployment model
Every business has unique needs, and choosing the right cloud deployment model can help you gain a competitive advantage. Here’s how you can evaluate the right model given your organization’s requirements:
- Governance and self-service for users – The cloud must strike a balance between the user’s need to accomplish goals with executive-level needs to hold down costs and maintain a predictable environment. Self-service allows for faster resource provisioning that speeds up the pace of business, while a proper governance regime maintains reliable service for everyone.
- DevOps and CI/CD – These terms are often conflated, but they represent two different concepts. DevOps refer to an organization’s decision-making and ownership culture, while CI/CD (continuous integration/continuous development) refers to how application lifecycles are managed.
- Containers and cloud platforms – Container solutions like Docker and Kubernetes offer strong dev/test capabilities, while platforms like Cloud Foundry offer additional service layers that require more complex governance. Understanding the difference will affect both the user experience and overall management of the cloud.
- Standardization and certification – For mission-critical apps in particular, all clouds must be certified for performance, security and other factors, and this applies to any cloud that the primary cloud might use for back-up and sharing.
- Location – Large organizations will need a geographic deployment strategy for international operations to ensure that data and services can be hosted as close to users as possible.
Implementing a cloud deployment model
Mendix supports Cloud Foundry, Docker and Kubernetes, which means it supports both self-service options and broad data governance equally well. In addition, we support CI/CD and its integration into our clients’ default culture to ensure resources can be consumed easily without broader disruption to data operations.
Mendix also utilizes a multi-cloud strategy, which is helpful when it comes to certification and location-based provisioning. For clients that are not already utilizing hyperscale resources from Azure, Amazon and others, we can provide a faster and less complicated certification process, while at the same time delivering equal value using open Cloud Foundry and Docker environments.
For international organizations that require cloud support across geographic boundaries, Mendix provides either public cloud services on shared resources or virtual private networks (VPNs) with self-service capabilities. In this way, users can select the services they require at the desired level of shielding.
Learn more about choosing the right Mendix cloud deployment model for your organization and how to enhance your emerging cloud strategy.