Mastering software architecture, technology leadership, and engineering excellence. The Architect View Master approach helps you understand systems from every viewpoint: business, technical, operational, and strategic.
Insights and perspectives on solution and software architecture
Wardley Mapping turns build vs buy debates into a reviewable text file. Draw a Wardley map as code, mark what blocks change, and keep it beside your ADRs.
Eventual consistency in DDD works when the inconsistency window is a business number. Build a .NET saga with outbox and idempotent consumers, then alert on it.
Post-quantum cryptography migration can't wait for quantum computers. Run this 20-minute OpenSSL check on your own TLS endpoints today.
Chaos engineering means breaking systems on purpose to test failure predictions. Here is a real Chaos Mesh walkthrough on a local kind cluster.
Axe-core catches about 57% of accessibility issues by one count. Here is what it cannot see, and who should own the rest.
Organizational understanding decides whether a capability lands. The technology ships and works, but the organization never adapts, so it sits unused.
Agentic fitness functions use a calibrated AI agent to judge architecture drift a script cannot, and post a verdict without blocking the build.
Free resource
A 48-page PDF with 26 diagrams on reasoning about trade-offs, drawing better boundaries, and picking the right pattern for the problem in front of you. Every pattern comes with the price you pay for it.
A short round-up of the month's articles on architecture trade-offs, boundaries, and the patterns worth their price. No drip sequence, no filler, one send.
No spam, unsubscribe anytime.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.