96 docs tagged with "architecture"

Logical, process, physical, development views and use case scenarios

Map bounded contexts to service boundaries for optimal architecture

Template for documenting architecture decisions including context, rationale, consequences, and alternatives. Enables searchable decision history and informed future decisions.

Capture decisions, rationale, alternatives, and traceability

Establish clear principles and standards that guide decisions while allowing team autonomy and innovation.

Comprehensive architecture review guide covering quality attributes assessment, risk identification, operational readiness, technology fitness evaluation, and team capability assessment.

Design systems that can demonstrate compliance and security through comprehensive logging and tracing.

Content delivery networks, edge caching, and geographically distributed compute

Guide teams through major architectural changes using proven change management techniques.

TL;DR

TL;DR

Comprehensive guide to cloud-native architectures, compute models, orchestration, networking, and deployment topologies

Reference architectures for typical application patterns

Reusable components, design tokens, and living documentation

Favor object composition over inheritance to achieve flexibility, reduce fragility, and improve code reuse.

VMs, containers, and serverless platforms—trade-offs in isolation, performance, cold start, and operational complexity

Assign system event handling to a non-UI class that mediates between UI and domain logic

Align team structure to system architecture: organizations produce designs reflecting their communication structure.

TL;DR

Separate read and write models to optimize for different access patterns and enable flexible data transformation.

Understand how sections connect and key linkages between topics across the handbook.

Master modern data architecture patterns, storage technologies, and scalable persistence strategies

Manage where data physically resides and who can access it, respecting legal boundaries and customer requirements.

Isolate service data with dedicated databases to maintain independence and prevent tight coupling.

TL;DR

High-level modules should not depend on low-level modules; both should depend on abstractions. Invert the dependency flow.

Single-region, multi-region, active-active, active-passive, and disaster recovery patterns

Backup strategies, RPO/RTO, PITR, and failover testing for business continuity

Services that call each other synchronously in sequence, creating tight coupling and monolith behavior.

Master distributed systems architecture, communication patterns, and resilience strategies for building scalable, fault-tolerant systems.

Architecture decision records, views and viewpoints, diagramming, and reference architectures

Strategic and tactical design techniques to model complex domains and align software with business

TL;DR

Store the complete history of changes as immutable events rather than storing only the current state.

TL;DR

Create a lightweight process for justified deviations from standards without compromising overall coherence.

TL;DR

Ground yourself in core architecture, systems thinking, paradigms, and data basics to make sound design decisions.

Frontend patterns, mobile design, state management, performance, and offline capabilities

Component design, state management, rendering strategies, and performance optimization

Comprehensive reference of software architecture terminology, acronyms, and concepts. Includes SLA/SLO/SLI, RBAC/ABAC, bounded contexts, sagas, and design patterns.

TL;DR

Build systems where components relate strongly to their purpose while remaining loosely connected to other components.

Understand the international standard for software product quality and map it to practical architectural decisions.

Master the Principle of Least Knowledge to reduce coupling and improve maintainability in complex systems.

TL;DR

TL;DR

Independent, deployable frontend components for large teams

TL;DR

TL;DR

MVVM, offline sync, background tasks, battery/network constraints, and app distribution

Apply modularity principles, information hiding, and sound module design to reduce coupling, improve cohesion, and enable independent system evolution.

TL;DR

TL;DR

Geographic redundancy patterns, consistency trade-offs, and traffic routing

Design data isolation strategies for SaaS systems: shared vs dedicated resources

Compare architectural patterns for separation of concerns and testability

ViewModel, use cases, and repository patterns for maintainable mobile code

Services too small to be useful, requiring many inter-service calls and creating excessive complexity.

Zero-trust networking, encryption in transit, and certificate management

Load balancing, network policies, mTLS, and CDN/edge patterns

Software entities should be open for extension, closed for modification. Design for change without breaking existing code.

Scheduling, service discovery, load balancing, and stateful workload management

Every inter-service communication is synchronous, creating blocking dependencies and reducing resilience.

TL;DR

Scale data systems for growth: caching, replication, sharding, and materialized views

TL;DR

Image and artifact management, supply-chain security, cost controls, and resource quotas

Ensure architectural decisions support product goals and vice versa, avoiding misalignment that harms both.

How to choose and combine programming paradigms per component to meet quality attributes like latency, correctness, and evolvability.

Master the ISO/IEC 25010 model and implement performance, reliability, maintainability, testability, usability, and cost-efficiency.

Distribute read traffic across replicas while maintaining consistency

Common stacks, checklists, risk registers, and mitigation plans

Navigate the landscape of regulatory requirements and ensure architectural decisions support compliance.

Conduct effective architectural reviews that catch risks early without becoming approval bottlenecks.

Evolve data schemas safely without breaking clients as systems change over time.

Offload complex searches and analytics to specialized systems for performance

Specialize in cross-cutting concerns: security posture, data governance, and platform reliability.

Design systems where different areas address different aspects of functionality, improving modularity and maintainability.

Event-driven compute, auto-scaling, and pay-per-execution with no infrastructure management

TL;DR

DNS-based service discovery, load-balanced ingress, traffic routing, and egress control

Visualize service dependencies and communication patterns to understand system topology.

TL;DR

Multiple services accessing the same database directly, creating coupling and preventing independence.

Design coherent systems within organizational constraints, balancing business goals with technical feasibility.

TL;DR

Deep-dive into architecture patterns for real-time systems, streaming, IoT, ML, compliance, gaming, embedded, fintech, e-commerce, and social platforms

Explore different database and storage technologies: RDBMS, NoSQL, graphs, time-series, and more

Compose objects into larger structures while keeping relationships flexible and decoupled

Guide team-level technical decisions, mentor engineers, and ensure architectural patterns are applied correctly.

Manage technology lifecycle from adoption through deprecation with clear timelines and migration paths.

Design comprehensive testing strategies aligned with quality attributes and risk.

Coordinate distributed transactions across services using choreography and orchestration patterns.

Full OS isolation, live migration, mixed workloads, and legacy application compatibility

High-impact, hard-to-reverse decisions that shape system structure, qualities, and evolution.