feat: AIP-121 – Resource-oriented Design #42
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| - The operations (verbs) each resource provides, relying as much as possible on | ||
| the standard operations. | ||
|
|
||
| ### Resources |
There was a problem hiding this comment.
A couple of immediate questions...
- How would a "join" query look that faults in resources that cross multiple domains? Should this definition include some notion of composition?
- I'm going to assume that a resource includes multiple "sub resources" (e.g. order header plus order lines with additional reference/inclusion-of other resources (e.g. shipping and billing address for customer). How will this fold in here?
gibson042
reviewed
Aug 17, 2021
gibson042
reviewed
Aug 17, 2021
lukesneeringer
commented
Aug 17, 2021
lukesneeringer
commented
Aug 17, 2021
lukesneeringer
commented
Aug 17, 2021
aip/general/0121/aip.md
Outdated
|
|
||
| Resource-oriented APIs emphasize resources (data model) over the operations | ||
| performed on those resources (functionality). A typical resource-oriented API | ||
| exposes a large number of resources with a small number of operations on each |
There was a problem hiding this comment.
an arbitrary number
lukesneeringer
commented
Aug 17, 2021
aip/general/0121/aip.md
Outdated
| verbs (usually `POST`) and define the custom verb in the URI. See AIP-136 for | ||
| more detail. | ||
|
|
||
| Services **should** prefer standard operations over custom operations; the |
There was a problem hiding this comment.
This is the spot to include the guidance about including all the standard operations unless you have a reason.
Co-authored-by: Richard Gibson <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.