Cloud agnostic architecture enables applications to migrate seamlessly across various cloud platforms, offering freedom from vendor lock-in and flexibility in provider choice. It involves using containerized workloads and Kubernetes for service deployment but poses challenges such as building custom data centers and potential limitations in service capabilities. Effective strategies include adopting a loosely coupled architecture and having a clear exit strategy to mitigate risks of vendor dependence.

1. #techtuesdays
The Cloud Agnostic
Architecture

2. #techtuesdays
What is Cloud Agnostic
Architecture?
Cloud agnostic refers to a cloud design strategy
in which applications, tools, and services are
designed to migrate seamlessly between
multiple cloud platforms influenced by changes
in pricing, performance, or offerings.

3. #techtuesdays
Why Enterprises Want Cloud
Agnostic Architecture?
Seamless migration from one cloud provider
to another.
Choice of cloud provider depending on pricing.
Freedom from vendor lock-in.

4. #techtuesdays
Structure of a Cloud Agnostic
Architecture
All services are built by the customer as containerized
workload (Docker images) and deployed on the kubernetes
cluster offered by the provider.
SERVICE SERVICE SERVICE SERVICE SERVICE
ELASTIC KIBANA GRAFANA
KAFTA KEYCLOAK PROMETHEUS
MYSQL RABBITMQ ---
Kubernetes as the common abstraction
Any cloud provider
Product
service
Selfhosted infrastructure
components
Cloud
platform

5. #techtuesdays
How Applications Switch from
One Provider to Another
Service Service Service Service Service
Elastic
Elastic
Kafta
Kafta
MySQL
MySQL
Kubernetes as the common abstraction
Kubernetes as the common abstraction
Microsoft Azure
Amazon Web Service
Kibana
Kibana
Keycloak
Keycloak
RabbitMQ
RabbitMQ
---
---
Grafana
Grafana
Prometheus
Prometheus
Service
Service Service Service Service Service
Just move it
Just switch
from EKS to AKS
Cloud agnostic
part
Cloud
platform

6. #techtuesdays
Challenges of True Cloud
Agnostic Architecture
Building a custom datacenter instead
of leveraging the one provided by the
vendor.
Not tapping into the SaaS capabilities
of the cloud vendor.
Need of rewriting the entire
infrastructure code.

7. #techtuesdays
Challenges of True Cloud
Agnostic Architecture
If one provider offers fewer datacenter
locations than another, then we are
locked in.
Different networking capabilities of
different vendors.
High data egress charges.

8. #techtuesdays
Strategies for Avoiding
Vendor Lock-in
Follow loosely
coupled
architecture.
Choose a hybrid
cloud and
strategically select
what not to lock-in.
Have a clear exit
strategy up-front.

9. Thank you for
your time.
#techtuesdays www.Gleecus.com
hello@gleecus.com
Contact us: