Explained: AWS Fargate

You have a container. It runs on your laptop with a single docker run , it passes its tests, and it is ready for production. Then you open the AWS console to deploy it and the questions start. Which EC2 instance type? How many of them? Which AMI? Who patches the operating system next month? What happens when the cluster runs out of room at 2 a.m.? None of those questions are about your application. They are about the machines your application happ… Read More

Architecture: Docker

You ship a service that works perfectly on your laptop. It hits staging and dies immediately. The stack trace points at a shared library your machine had and the staging box did not. Someone on the team says the words every engineer has heard: "works on my machine." The old fix was a virtual machine. Package the whole operating system, ship the image, run it anywhere. It works, but you are shipping gigabytes of kernel and userland to so… Read More

Architecture: AWS Fargate

You have a containerized service. You want it running in AWS. You create an ECS cluster, write a task definition, and hit deploy. A minute later, your container is up and serving traffic. You never touched a server. That convenience hides a remarkable amount of engineering. Somewhere in AWS, a scheduler decided where your task would run, a microVM was created and booted in milliseconds, a network interface was injected into your VPC, and your con… Read More