Tag
Posts related to architecture, ordered from newest to oldest.
A practical guide to when a modular monolith is the right long-term architecture, and why it is often better than premature microservices for small teams.
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 improving a monolith incrementally, including boundary cleanup, ownership, deployment friction, and how to make real progress without forcing a rewrite.
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 idempotency in event-driven systems, including retries, duplicate delivery, state changes, and why small teams should design for it early.
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 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 deciding when a service boundary helps, when it adds operational drag, and how small teams can avoid splitting systems too early.
A practical guide to technical leadership in messy systems, including how to lead architecture, delivery, and risk reduction without waiting for the system to become clean first.
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 where AI belongs in product workflows, where deterministic logic should stay in control, and how small teams can use AI without making the whole product probabilistic.
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 to platform engineering for small teams on AWS, including what to build, what to avoid building too early, and why SST is a flexible and manageable infrastructure-as-code choice.
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.