Modular Hexagonal DDDDomain-Driven Design

Core 1.0.0-draft

Modular Hexagonal Domain-Driven Design

A portable standard for replaceable bounded-context modules — Domain at the center, ports at the edge, hosts as adapters. Frameworks map Core — none of them is Core.

Enter Core Adopt in your project
If the peer module is deleted and replaced by HTTP, does Application and Domain still compile?
Layer 01

Core

Framework-agnostic rules: layout, strictness, golden flow, ACL, and events.

Layer 02

Adapters

How Core maps onto hosts — Laravel, Symfony, Yii, CI, CakePHP, Spiral, Slim, Mezzio.

Layer 03

Cookbook

One Ordering ↔ Warehouse story that shows sync ACL and async events end-to-end.

Start here

  1. Portable requirements — MUST checklist for any host
  2. Philosophy · layout · strictness
  3. Golden flow then ACL / Events
  4. Greenfield bootstrap or Ordering ↔ Warehouse cookbook
Modular Hexagonal Domain-Driven Design
Core 1.0.0-draft