Design serverless apps for reliability, cold start, and cost. Event-driven patterns and observability.
Serverless fits event-driven and variable load. Use these practices to keep it reliable and cost-effective.
Best practice: treat Lambda as a building block; design event contracts and failure modes up front.
Get the latest tutorials, guides, and insights on AI, DevOps, Cloud, and Infrastructure delivered directly to your inbox.
We've shipped three end-to-end ML systems. The pieces that look obvious in slides and turn out to be the actual work.
Concrete systemd unit patterns that reduced flakiness: restart policies, resource limits, and structured logs.
Explore more articles in this category
There are two hard problems in computer science." We've worked on the cache-invalidation one for a while. The patterns that hold up at scale and the ones that look clean and aren't.
We use Step Functions for batch processing, document ingestion, and a few agentic workflows. The patterns that work, the limits we hit, and where we'd reach for something else.
After two years of running Karpenter on production EKS clusters, the NodePool patterns that survived, the ones we replaced, and the tuning that matters.