By designing cloud native solutions from the beginning, businesses can maximize the full potential of the cloud instead of struggling to adapt existing architectures.

Completely new way of designing application architectures was invented, when cloud stepped into the game. What we call cloud native architecture is approach, which uses containers for running workloads, deployed as microservices and managed on elastic infrastructure through agile DevOps processes and continuous delivery workflows.

Before cloud, we had physical infrastructure and on top of it we had VMs. This was our first step towards virtualization, but we still had to be managing physical server under our VMs. With EC2, there was no longer needed to administer physical infrastructure, and we only used power of virtualized machines. With container, we bring virtualization of our solutions to completely new level! Having many microservices handling specialized task without the need of taking care of underlying architecture. This is what lets developers to stay focused on delivering creative and innovative solution, rather than wasting time on configuring their environment.

Another great advantage of being cloud native is efficient usage of services, and thus driving you costs to only what is necessary at particular point of time. With services like AWS Elastic Container Service (ECS) and Kubernetes Service (EKS) and using AWS Fargate to orchestrate underlying infrastructure, you will make sure, that your solutions are using only as much, as is currently needed! Picture below describes the behavior of the provisioning of Fargate’s container to handle demand comparing to EC2 usage.