Use cases are infrastructure-layer concern agnostic. If we design them as little modules that as long as we can provide the correct inputs, they'll know how to execute the features of our system, they can stay agnostic to what API style executes them.
You'll notice that in the DDDForum codebase, a single
useCase/ folder has several files in it. Each folder has the Controller, the DTO, the
UseCaseErrors, and the Use Case…
This book’s mission is to teach developers the essential skills and practices to write testable, flexible, and maintainable code.
You can read more about the learning journey in the "Software Design and Architecture Roadmap 🖼️".
Already bought it?
If you’ve already purchased the book, click here to re-send your link. You can read the online wiki or download a copy of the book in PDF, EPUB, and Kindle versions.
You can read the intro to the book for free and visit solidbook.io to buy the book/wiki (it's currently on pre-sale for 33% off)! For recent updates, click here. To get an idea of my writing, read some of my best free content here and here.