ArchitecturePatterns

How the whole system is shaped — the umbrella choice that everything else (Compute, Networking, Data) gets built inside of.

Why we need this / what value this brings

The system's overall shape determines deploy coupling, team scaling limits, and how expensive change becomes later — getting it roughly right early avoids a costly rewrite.

When to use this

Revisit deliberately at major inflection points (team growth, a component needing independent scaling) — not by default on every project.

How to use or implement this

Start with the simplest shape that fits current team size and load, and only add structure (modules, then services) when a concrete pain point demands it.

Subtopics

• CQRS
• EventDriven
• Layered N Tier
• Microservices
• ModularMonolith
• Monolith
• PeerToPeer
• SOA
• Serverless
• SpaceBased

Research questions

• Localz today: is it closer to a modular monolith or already drifting toward microservices? Which is right for its current team size?

---

Empty folder — drop notes, links, and findings here as you research.