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
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 2, 2023 at 7:09 | comment | added | Laiv | The question is never if you can do X. You always can do X, regardless of what others say. The real question is what would you be solving by splitting the URI this way. The what will dictate where the customer id will come from. | |
| Jul 1, 2023 at 0:38 | answer | added | VoiceOfUnreason | timeline score: 2 | |
| Jun 30, 2023 at 15:14 | answer | added | Rik D | timeline score: 0 | |
| Jun 30, 2023 at 15:14 | comment | added | Erik Eidt | It is not allowed. The DDD police will get you. | |
| S Jun 30, 2023 at 13:31 | history | suggested | Rohit Gupta | CC BY-SA 4.0 | Corrected typos |
| Jun 30, 2023 at 13:21 | review | Suggested edits | |||
| S Jun 30, 2023 at 13:31 | |||||
| Jun 30, 2023 at 12:56 | comment | added | user1937198 | If your Customer aggregate is small enough that you can retrive it all at once, why do you need a seperate orders endpoint, vs just having an /customers/1/orders that also returns all the products. Or to look at it the other way, if you need to split the API, does that not suggest that the aggregate root may be to big too be retrieved from the database for every operation, and so the orders should be split into a seperate aggregate root. | |
| Jun 30, 2023 at 12:36 | history | edited | Jacek | CC BY-SA 4.0 | edited title |
| S Jun 30, 2023 at 12:10 | review | First questions | |||
| Jun 30, 2023 at 12:32 | |||||
| S Jun 30, 2023 at 12:10 | history | asked | Jacek | CC BY-SA 4.0 |