#architecture

The AWS spend audit I do every quarter

“AWS doesn't optimize your bill. AWS optimizes their revenue. The two are not the same hobby.”

DynamoDB for time-series IoT — when the relational urge is wrong

“A Postgres query that does a sequential scan on six months of telemetry is a Friday-afternoon meeting waiting to happen.”

Lambda vs Fargate vs ECS — the napkin decision tree

“Cold-start tolerance is the question; everything else is a follow-up.”

MQTT as the house's nervous system — one broker, every device

“When every device speaks to one broker instead of to each other, killing a vendor's cloud API stops being a catastrophe and becomes a footnote. You lose one device's features, not the web. That's the whole point of a nervous system — you can lose a finger without losing the hand.”

How Instagram scales — what I learned from Mike Krieger's deck

“Most architecture failures I've seen weren't because the team picked the wrong tool. They were because the team picked the *exciting* tool when boring would have worked.”

What I stole from Netflix's Kafka data pipeline deck

“You don't need Netflix's scale to use Netflix's architecture. You just need to want the same things Netflix wanted: decoupling, replay, and one source of truth.”