Enterprise Architecture Patterns
Enterprise architecture provides the frameworks and patterns for organising complex technology estates — across applications, data, infrastructure, and integration. For large organisations with many systems and teams, enterprise architecture creates the shared standards and patterns that prevent the chaos of independent teams making incompatible choices.
Architecture Frameworks
- TOGAF: The Open Group Architecture Framework — the most widely used enterprise architecture framework. Provides a methodology (ADM - Architecture Development Method) and taxonomy. Heavy and process-oriented; useful in regulated industries and large enterprises.
- Zachman Framework: A schema for organising architectural artefacts across stakeholder perspectives and dimensions
- C4 Model (Simon Brown): Lightweight documentation framework — Context, Container, Component, Code diagrams. Practical and widely adopted for documenting software architecture.
Common Architectural Patterns
- Microservices: Decomposed services with independent deployment. High operational complexity, high team autonomy.
- Event-driven architecture: Services communicate via events — loose coupling, good for async workflows
- CQRS (Command Query Responsibility Segregation): Separate read and write models — good for high-read, complex-domain systems
- Strangler Fig: Incrementally replace legacy systems — practical migration pattern
- API Gateway: Centralised API management for microservices estates
Architecture Governance
Architecture Review Boards (ARBs) or Architecture Guilds review significant architectural decisions, maintain standards, and resolve cross-team architectural conflicts. Lightweight governance through Architecture Decision Records (ADRs) captures decision rationale and creates institutional memory.