Skip to content

svallejo-dev/architecture

v0.5.0MIT

Large-scale systems design, starting from what already exists or, without metrics, from the business archetype: system design sparring as a delta (AS-IS → TO-BE → migration) or a PoC plan, a parallel red team, capacity computed in code with scenarios and thresholds, DDD strategic design, business archetypes and a curated catalog of building blocks.

strategic-design

Strategic design (DDD) to decide the boundaries of services and contexts: subdomain classification (core, supporting, generic), a context map with named patterns (Anticorruption Layer, Open Host Service, Published Language, Customer-Supplier, Conformist, Shared Kernel, Partnership, Separate Ways), data ownership and team alignment. It starts from the current map (AS-IS) before the target. Use it when discussing service boundaries, integrations between systems, a legacy migration, "context map", "bounded contexts", "subdomains" or "where does this responsibility go?".

License
MIT
Read SKILL.md at the source

Pinned to revision a2c346f89684, so it is the text this page describes rather than whatever the author pushed since.

Files

Every link opens the file at its source, pinned to the revision this page describes.