Search

Find insights, training programs, and workshops

Common Architecture Patterns
Intermediate (SA, EA)5-7 hoursPattern selection guide + pattern comparison matrix + anti-pattern catalogue

Proven, reusable solutions to recurring structural problems — each with known trade-offs that make it suited to some contexts and unsuitable for others.

Quick Navigation Start here — What patterns are Layered architecture Microservices Event-driven architecture CQRS and event sourcing Hexagonal architecture Serverless Choosing...

1.5 DaysIntensive
PracticalSA · EA
Architecture in the Age of AI: What Can Be Automated — and What Cannot
Architecture in the Age of AI: What Can Be Automated — and What Cannot

A governance-driven perspective explaining why software architecture cannot be automated because decision accountability and consequence ownership cannot be delegated to AI.

...AI-accelerated environment The Question Everyone Is Quietly Asking If AI can generate code, design microservices, suggest cloud patterns, and simulate load scenarios — Do we still need architects? The...

Architecture Patterns That Travel Across Industries
Architecture Patterns That Travel Across Industries

The patterns that solve your hardest distributed systems problems were already solved — in a submarine, a postal sorting office, and an electrical panel. Most architects never look.

...in every ship built since. Now consider the software architect, one hundred years later. Designing a microservices platform. One service is taking on too much load. Failures are cascading. One overwhelmed...

The Minimum Architecture Every Company Needs: The House, the Hallway, and the Doorbell
The Minimum Architecture Every Company Needs: The House, the Hallway, and the Doorbell

A practical architectural model explaining why most companies only need a modular monolith, a workflow orchestrator, and outcome-based events.

...Complexity Trap Modern architecture discussions quickly become complicated. Teams start talking about: Microservices Event-driven systems Message brokers Workflow engines Distributed orchestration Before...

Context-Driven Architecture: Why Software Design Must Adapt to Business Geography
Context-Driven Architecture: Why Software Design Must Adapt to Business Geography

Just as buildings must adapt to snow, desert, or tropical climates, software architecture must align with business geography to improve predictability and reduce complexity.

...climates --- and expect stability. The Quiet Collapse in Software Systems A mid-sized enterprise adopts a microservices architecture inspired by high-scale technology firms. On paper, it looks modern. Distributed....

Architectural Decision Records (ADR): The Missing Layer Between Strategy and Implementation
Architectural Decision Records (ADR): The Missing Layer Between Strategy and Implementation

A practical guide explaining why Architectural Decision Records (ADR) are the missing link between enterprise architecture strategy and engineering implementation.

...Context What problem are we trying to solve? Example: "We need a reliable communication mechanism between microservices." Options Considered What alternatives were evaluated? Example: REST APIs Message queues...

Enterprise, Solution, and Technical Architects: Who Does What in a Context-Driven Architecture?
Enterprise, Solution, and Technical Architects: Who Does What in a Context-Driven Architecture?

A structured executive guide explaining the difference between Enterprise, Solution, and Technical Architects using Context-Driven Architecture to clarify responsibilities and reduce structural misalignment.

...They define the environmental rules. Risk of Failure If Enterprise Architecture misreads geography: Microservices are adopted in stable environments Event streaming is forced without volatility AI autonomy...

Architecture Decisions & ADRs
All levels — SA, EA, TS3-4 hoursADR template + decision log + rationale guide

How to capture, document, and govern architecture decisions using ADRs — the lightweight mechanism that turns tribal knowledge into shared understanding.

...did we choose Kafka over RabbitMQ?" — "I think Sarah decided that, but she left." "We decided to use microservices" — "When? Who approved that?" "The architecture says X but the code does Y" — no one documented...

Half-dayIntensive
PracticalReady to use
Current State & Target State Architecture
All levels — SA, EA, TS4-5 hoursAs-is / to-be architecture canvas + transition state design + maturity scale + AI readiness assessment

How to document what exists today, define what must exist tomorrow, and design the transition states that get you there — the discipline of architecture that connects present reality to future goals.

...just migrate to the new platform" — without understanding what's on the old one. "The target state is microservices" — without knowing the monolith has 40 integration points. "We'll replace the legacy system"...

1 dayIntensive
PracticalCanvas exercise
Operating Model Choices
Advanced (EA, TS)5-6 hoursOperating model design canvas + team topology guide + Conway's Law application worksheet + Communication Structure Heatmap

How the structure of technology teams shapes the structure of the systems they build — covering Conway's Law, centralised vs federated models, platform teams, product operating models, team topologies, and designing the organisation that produces the architecture you want.

...organisation, design the organisation to produce the system you want. Desired system: independently deployable microservices. Required team structure: small, autonomous teams that own services end-to-end. Desired...

1 DayIntensive
StrategicEA · TS