The questions that come up in almost every cloud architecture review I run — compute, ownership, security, data, networking, resilience, operations and cost — …
Architecture (14)
What to bring to a cloud architecture review so it's one meeting, not three: entry criteria, the diagrams reviewers need, the cross-cutting concerns people …
A simple order of preference for where code runs — SaaS, serverless, containers, servers — why each rung up removes work, and how to design the ideal version …
Seventeen patterns I flag again and again in cloud architecture reviews — glue-code functions, synchronous long jobs, polling, credentials on disk, jump hosts — …
How to draw cloud architecture diagrams that answer questions before they're asked, and a lightweight architecture decision record (ADR) template for the …
How a central cloud team can help dozens of teams build well without becoming a bottleneck: configuration as a service, compliance as code, reusable IaC …
Hands-on notes and code for AWS Guidance.
Deep dive on all things AWS Well-Architected
Capture all changes to an application state as a sequence of events.
Learning by building: Diagrams(Diagram as Code), lets you draw the cloud system architecture in Python code
Learning by building: Graphviz - Graph Visualization Software
A serverless architecture is “typically” composed of many services. The following covers the key considerations and configuration options for the most common …
A personal cheatsheet/reference for cloud native software architecture.