Use Cases
Concrete use cases for Jardis
Brownfield or Greenfield: the Entry Point Determines the Strategy
DDD-based code generation is not a tool that only works on a blank slate. The majority of production PHP systems have a history: grown codebase, framework dependencies in the wrong layer, no explicit domain boundaries. Brownfield migration does not mean rewriting the system — it means building new functionality on a clean architecture while the existing system keeps running.
For greenfield projects the advantage is different: the architecture is consistent from sprint 1. New Bounded Contexts are generated rather than hand-coded, which means the team starts with business logic immediately instead of infrastructure. Multi-team development benefits from every context being structured identically — onboarding onto a new Bounded Context takes hours rather than weeks.
Microservices extraction, modular monolith, API-first development: each scenario has distinct requirements around timing and sequencing. The pages below describe the concrete workflow for each use case — which contexts get generated when, how integration into existing systems works, and when each approach is the right choice.