Patterns

Patterns are compositions of the primitives you’ve already met — stacks, constructs, feature toggles, SSM wiring — arranged to solve a recurring architectural problem. These pages are deliberately honest: where a pattern maps to concrete composer selections or an existing example, they say so; where a pattern is a composition sketch with no shipped example, they say that too, rather than implying a turnkey feature.

The patterns

• Multi-Tenant — isolating tenants in one deployment.
• CQRS — separating the write and read paths.
• Event-Driven — decoupling with queues, topics, and buses.

Read these after the guides

Patterns assume you’re comfortable with the guides — they don’t re-explain how to declare a table or a queue, they show how to arrange several of them. Every pattern stays within the framework’s contracts: config/lambdas.ts and config/tables/index.ts as the only user-code contracts, and SSM-only cross-stack wiring.