Timeline for Is it allowed in DDD application to expose HTTP API endpoints for objects different than aggregate roots?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 4, 2023 at 8:25 | comment | added | guillaume31 | @RikD not really clearer. My point was that you might be letting DDD concerns (consistency boundary/transactional) leak down to the HTTP side of things. If a user wants to change an Order, why shouldn't the endpoint be /orders/..., regardless of what happens under the hood afterwards? But I'd gladly let myself be convinced of the opposite, hence the question marks... | |
| Jun 30, 2023 at 16:23 | comment | added | Jacek | Thank you, it makes sense. I know that domain part shouldn't be too tightly coupled with other application layers, such as REST API for example. On the other hand I want both layers to work with my applicaton purposes: domain to fulfill business requirements and http api to fulfill clients needs. It's difficult to find a good balance. | |
| Jun 30, 2023 at 15:33 | comment | added | Rik D | @guillaume31 updated the answer, is it more clear now? | |
| Jun 30, 2023 at 15:28 | history | edited | Rik D | CC BY-SA 4.0 | added 6 characters in body |
| Jun 30, 2023 at 15:18 | comment | added | guillaume31 | But HTTP resources are at the confluence of functional and technical concerns. Should the consistency boundary leak out down to that level? Should API clients know about it? | |
| Jun 30, 2023 at 15:14 | history | answered | Rik D | CC BY-SA 4.0 |