The latest articles on DEV Community by Ravisankar.ponugoti (@ravisankar_p_4f803a7ee688). https://dev.to/ravisankar_p_4f803a7ee688 https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4099311%2F74562cb0-449c-4d82-980e-5bc4d0ce6a1d.png https://dev.to/ravisankar_p_4f803a7ee688 en Ravisankar.ponugoti Thu, 24 Sep 2026 19:14:45 +0000 https://dev.to/ravisankar_p_4f803a7ee688/modernizing-public-sector-applications-using-serverless-and-containers-4hmm https://dev.to/ravisankar_p_4f803a7ee688/modernizing-public-sector-applications-using-serverless-and-containers-4hmm <p>100,000 students. One "Enroll" button. 🎓</p> <p>Here's how I'd design the backend on AWS using serverless, events, and containers 👇</p> <p>1️⃣ The request</p> <p>Student → Website → API Gateway → Lambda</p> <p>Lambda checks the basics: is the student valid, is the course open, is enrollment allowed? There's no server to keep running 24/7. It runs when a request arrives, and AWS handles scaling and patching.</p> <p>2️⃣ The trap</p> <p>Once enrollment succeeds, it's tempting to have Lambda call Payment, the student database, email, faculty alerts, and analytics directly. That's tight coupling. If the email service goes down, the whole flow can suffer.</p> <p>3️⃣ The fix: publish an event</p> <p>Instead of calling everyone, Lambda announces one thing: "StudentEnrolled" 📣</p> <p>Lambda is the producer, EventBridge is the broker, and the Payment, Database, and Notification services are the consumers.</p> <p>Producer produces → Broker distributes → Consumer consumes.</p> <p>Want fraud detection or analytics later? Add a new consumer. The enrollment service doesn't change. That's loose coupling.</p> <p>4️⃣ Where containers come in</p> <p>Say the Payment service grows into Java, Spring Boot, libraries, and a payment SDK. Package it all into a container, then choose where it runs:</p> <p>☸️ EKS if your team already runs Kubernetes</p> <p>🚢 ECS if you want AWS-native orchestration with fewer decisions to make</p> <p>5️⃣ Where Fargate fits (where many beginners get confused)</p> <p>ECS and EKS decide how your containers are orchestrated. Fargate is the serverless compute underneath, so you don't manage, patch, or scale servers.</p> <p>My one-line memory hook: Lambda = serverless code, Fargate = serverless containers.</p> <p>What would you plug in as the next consumer of the StudentEnrolled event?</p> <h1> AWS #Serverless #SystemDesign #EventDrivenArchitecture #Containers </h1> serverless aws