Technology

DDD patterns and architecture concepts that Jardis generates as physical structure in PHP

Hexagonal Architecture. By Default, Not by Accident.

Jardis generates hexagonal architecture for every Bounded Context: ports, adapters, application services, domain layer. Correct PHP structure from line one.

Learn more

Implement CQRS in PHP. The Right Way.

Jardis generates CQRS in PHP: CommandDTO, QueryDTO, handlers, typed response objects, read/write splitting. Structurally enforced, not just a convention.

Learn more

Bounded Contexts in PHP. Physically separated, not just conceptual.

Standalone PHP packages per domain: Jardis generates Bounded Contexts with physical separation at the filesystem level, communication via contracts and events.

Learn more

Firing events is easy. Making them arrive is not.

Domain events as first-class citizens in PHP: Jardis generates typed events with automatic queue publishing, no manual event schema management.

Learn more

Your repository has 47 methods. That's the problem.

5-stage repository pipeline in PHP: Jardis generates separated read/write paths with dedicated interfaces, physically enforced. No God Classes, no ORM coupling.

Learn more

Your project screams Laravel. Not your domain.

Jardis enforces Clean Architecture in PHP: Dependency Rule anchored in the folder structure, framework independence guaranteed, business logic fully isolated.

Learn more

DDD Patterns as Executable PHP, Not as Documentation

In most teams, Domain-Driven Design lives in documentation. Bounded Contexts are Miro boards. CQRS is a convention in the wiki. Event-Driven Architecture is a slide deck from the last architecture review. What reaches production code regularly deviates from the patterns — not because developers misunderstand the concepts, but because boilerplate burden and time pressure prevent consistent implementation.

Jardis materializes these patterns as physical file structure. A Bounded Context is not a label on a diagram — it is a separate PHP package with its own namespace and no transitive dependencies outward. An Aggregate Root is not a convention — it is a generated class with explicit consistency boundaries. The Repository Pattern separates domain from persistence at the file level: the domain layer contains no Eloquent, no Doctrine.

Clean Architecture, CQRS separation, event-sourcing readiness: these patterns are not optionally configurable — they are the output. The pages below explain what each pattern means and what it looks like as concrete PHP code produced by Jardis.