Step 3: Identify your data-access patterns
This example use case has the following access patterns for managing relationships between different car components.
Access pattern | Priority | Read or write | Description | Type | Filters | Result ordering |
|---|---|---|---|---|---|---|
Immediate child | High | Read | Retrieve all the immediate child components for a parent component ID. | Multiple |
| N/A |
All child components | High | Read | Retrieve a recursive list of all child components for a component ID. | Multiple |
| N/A |
Ancestors | High | Read | Retrieve the ancestors of a component. | Multiple |
| N/A |
