architectural-pattern
13 skills · 11 free · cap $19/skill or unlock all for $99
architecture-paradigm-layered
IncludedApplies layered n-tier architecture with enforced boundaries. Use when designing moderate systems needing clear presentation, domain, and persistence layers.
architecture-paradigm-microservices
IncludedApplies microservices for independent deployment and per-service scaling. Use when teams need autonomous release cycles with distinct capability scaling needs.
architecture-paradigm-client-server
IncludedApplies client-server architecture for web/mobile apps. Use when designing systems with centralized backend services, trust boundaries, or offline-first sync.
architecture-paradigm-cqrs-es
IncludedApplies CQRS and Event Sourcing for read/write separation and audit trails. Use when designing systems with complex domain logic or full state-change history.
architecture-paradigm-event-driven
IncludedApplies event-driven async messaging to decouple producers and consumers. Use when designing real-time or multi-subscriber systems needing loose coupling.
architecture-paradigm-functional-core
IncludedApplies Functional Core, Imperative Shell to isolate logic from side effects. Use when business logic is entangled with I/O or unit tests are slow and brittle.
architecture-paradigm-hexagonal
IncludedApplies hexagonal architecture isolating domain from infrastructure. Use when designing systems where testability and port/adapter separation are priorities.
architecture-paradigm-microkernel
IncludedApplies microkernel architecture with minimal core and plugin extensibility. Use when building platforms where third parties extend core functionality.
architecture-paradigm-modular-monolith
IncludedApplies modular monolith with enforced internal boundaries. Use when teams want service-level autonomy without distributed system overhead.
architecture-paradigm-serverless
IncludedApplies serverless FaaS patterns for event-driven workloads. Use when designing bursty workloads with minimal infrastructure and pay-per-execution cost model.
architecture-paradigm-service-based
IncludedApplies coarse-grained service architecture for deployment independence. Use when independent deployment is needed but shared databases rule out microservices.
architecture-paradigm-pipeline
IncludedApplies pipes-and-filters for sequential data transformations. Use when data flows through discrete stages like ETL, streaming analytics, or CI/CD pipelines.
architecture-paradigm-space-based
IncludedApplies data-grid architecture for high-traffic stateful workloads. Use when a single database cannot scale and in-memory partitioning is needed.