Timeline for Conceptual mismatch between DDD Application Services and REST API
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 30, 2017 at 3:39 | comment | added | ivenxu | @Den's comment on the original question provides alternative for this. Personally, I prefer that solution. REST and CQRS are more harmony and nature. This answer is good technique if our design doesn't have CQRS in play. However, I don't agree one the point of "at least in Spring/Java EE it's not a problem to create larger transaction from several methods". If we chain these separated operations together, then why we need separate them in the first place? | |
| Apr 30, 2015 at 2:35 | vote | accept | astreltsov | ||
| Apr 26, 2015 at 18:00 | comment | added | qbd | Yes, in relational dbs this will probably translate to multiple queries. Arbitrary nesting is supported by JSON API, it is described here: jsonapi.org/format/#fetching-includes | |
| Apr 26, 2015 at 17:46 | comment | added | astreltsov | What if more than one level of nesting is necessary? | |
| Apr 26, 2015 at 17:44 | comment | added | astreltsov | So a single GET request on the server translates into one or more actual queries (depending on how many sub-resources are included) which are then combined into a single resource object? | |
| Apr 24, 2015 at 9:12 | comment | added | qbd | No, I don't have read-only de-normalized representations. I use jsonapi.org standard and it has a mechanism to include related resources in the response for given resource. Basically I say "give me User with ID 1 and also include its subresources email and activation". This helps with getting rid of extra REST calls for subresources and it doesn't affect complexity of client dealing with the subresources if you use some good JSON API client library. | |
| Apr 24, 2015 at 9:05 | comment | added | astreltsov | That's what I've been thinking as well - create more granular resource representations because they are more convenient for write operations. How do you handle querying of resources when they become so granular? Create read-only de-normalized representations as well? | |
| Apr 24, 2015 at 9:01 | review | First posts | |||
| Apr 24, 2015 at 12:33 | |||||
| Apr 24, 2015 at 8:59 | history | answered | qbd | CC BY-SA 3.0 |