Programming, Software Engineer
The hard part of serverless is usually not writing the handler. It is understanding what failed, what the event looked like, and why the system changed underneath you.
Tag: serverless
Programming, Software Engineer
Clever infrastructure looks impressive in diagrams. Boring infrastructure is usually easier to operate, easier to debug, and much easier to keep alive once real users depend on it.
Programming, Software Engineer
AWS diagrams love to look simple. The problem is that the operational reality behind them is usually doing a lot more work than the picture admits.
Programming, Software Engineer
Serverless has real tradeoffs, but for small teams I still think it usually wins. The operational overhead stays low, the first version ships faster, and the mistakes are easier to afford early on.
Programming, Software Engineer
I still like serverless, but the tradeoff is obvious when something breaks at 2 a.m. The architecture is easy to ship and harder to reason about when you need logs, context, and a fast path to the real failure.