Evict the ORM From the Domain
Hard About 35 min Katabench Pro
The domain entity inherits the ORM's base class and carries its own mapping, welding the most stable layer to a persistence framework. Moving the mapping alone won't free it; you must sever the base-type coupling and invert the persistence concern out.
The full brief is part of Katabench Pro
Pro opens this kata's brief, its starter code and its grader. To see how the track works first, try Config Is Infrastructure, which is free.
How it is graded
You work across multiple files, and architecture rules turn the design boundaries into executable feedback.
What it practices
- Infrastructure as adapters
- Keep the ORM, clocks, caches, configuration and startup work out of the core as replaceable adapters.
Related katas
- Config Is Infrastructure Medium Free The shipping core reads a framework configuration type directly, welding the domain to infrastructure. Invert it behind a core-owned options port, and don't just rename the framework wrapper into the core, which trips a second rule.
- Caching Is an Adapter Medium Pro A quote use case memoizes prices with an infrastructure cache inside its own loop, so a storage tactic lives in the application. Move caching into a decorator on the price port, and let the composition root decide how long each cache lives.
- Keep Startup Out of Requests Easy Pro The search request path initializes its index on every call. Keep bootstrap work at the host boundary and lend the application only the initialized query capability.
- A Repository Out of Place Easy Pro A concrete
*Repositoryhas settled into the core, right next to the port it implements. Move the role to the layer where it belongs; renaming it to dodge the placement rule trips the naming rule instead.