Hi, I'm Binu.

I'm a cloud engineer working on AWS, growing toward solution architecture. Most of my time goes into the question underneath every design review: why this architecture, for this workload, rather than another one?

This site is where I work through that question in public. Each article starts from an architecture I have designed and diagrammed, then follows it the way a reviewer would — tracing requests through every component, checking how it scales, finding where it fails, and being explicit about what it costs to run and operate.

What I focus on

• Serverless and container architectures on AWS, and how to choose between them
• Request flow, scaling behaviour and where bottlenecks move as traffic grows
• Networking and security boundaries — VPCs, IAM, private origins and least privilege
• Reliability: multi-AZ design, failure handling, retries and idempotency
• Cost models and operational trade-offs, stated with their assumptions

How I write

I try to explain decisions rather than list services. I don't quote prices or quotas as facts, because they change and vary by account; when I use numbers, they are labelled assumptions for reasoning. And I don't treat the architecture with the most components as the most sophisticated one — usually the opposite.

About this site

The site is plain HTML and CSS with a few lines of JavaScript. It is served from a private Amazon S3 bucket through Amazon CloudFront using Origin Access Control, with an ACM certificate for HTTPS and DNS in Route 53 — a small, deliberately simple architecture of its own.