Cloud Agnostic Design
In this article, I’ll explain what cloud-agnostic design is, when it should be used, some strategies for designing cloud-agnostic systems, and finally a sample design to help you understand it better.
Nowadays the majority of the applications are deployed on public clouds. Cloud provider like AWS has more than 200 services, all catered for various use cases. That being said, having options of all major clouds such as AWS, Azure, and GCP it becomes difficult to choose the right option at the beginning.
Storage, compute, and networking are at the heart of any cloud infrastructure. In addition, managed, unmanaged, and serverless services are available across multiple clouds. This enables you to design your workloads to run in the cloud of your choice while also providing the flexibility to switch to other clouds. If you aim for cloud-agnostic design.
Note: While being cloud-agnostic provides flexibility, it also prevents you from using vendor-specific services that may provide cost and management overhead benefits.
Cloud agnostic designs:
- Allows you to avoid vendor lock-in.
- Provides a broader range of location availability.
- Makes it easy to design hybrid cloud solutions.
- The ability to easily migrate to another cloud provider.
