Tag
Posts related to aws, ordered from newest to oldest.
A practical guide to why EventBridge Pipes is so useful for lean teams, especially for reducing glue code in event-driven and serverless systems on AWS.
A practical guide to the manual operational steps small teams should eliminate early, before they become part of the delivery and operations culture.
A practical guide to idempotency in event-driven systems, including retries, duplicate delivery, state changes, and why small teams should design for it early.
Tags
Contact
If you are hiring, shaping a project, or need an experienced technical sounding board, use the contact form and send a little context.
Archive
A practical guide to using Hono for APIs on AWS, why it can be a better fit than API Gateway-heavy designs, and where the tradeoffs actually are for small teams.
A practical guide to SQS design for small teams on AWS, including retries, idempotency, DLQs, observability, and how to keep queue-based systems understandable.
A practical guide to when DynamoDB is the right choice for small teams, when it is not, and how to think about access patterns, cost shape, team familiarity, and serverless architecture tradeoffs.
A practical guide to what CloudFront SaaS Manager changes for multi-tenant SaaS platforms, especially around custom domains, tenant onboarding, edge routing, and operating serverless delivery at scale.
A practical guide to what CloudFront Functions KeyValueStore changes for serverless apps, including where it helps with edge routing, redirects, domain lookups, and lightweight request-time logic.
A practical guide to the first automations small teams should invest in on AWS, including deployments, infrastructure as code, secrets, checks, observability, and why SST is often a strong fit.
A practical guide to the cloud decisions worth making early, so teams do not end up choosing infrastructure, environments, runtime models, and operational patterns under delivery pressure.
A practical guide to the most common AWS mistakes small teams make in their first year, including IAM, environments, observability, cost visibility, networking, and choosing too much infrastructure too soon.
A practical guide to why AWS Lambda should be the default for small teams on AWS, where serverless fits best, how SST helps, and when to move to a more conventional service model.
A practical guide for startups and small engineering teams choosing between AWS Lambda, ECS/Fargate, EKS, and EC2 based on operational overhead, runtime needs, scaling patterns, and delivery speed.