[UXPROD-2739] Bulk APIs for Organizations Storage Module Created: 07/Oct/20 Updated: 05/May/21 |
|
| Status: | Open |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | New Feature | Priority: | TBD |
| Reporter: | Ian Walls | Assignee: | Ian Walls |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | bulk-api | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||||||||||
| Development Team: | None | ||||||||||||||||||||||||||||
| Kiwi Planning Points (DO NOT CHANGE): | 5 | ||||||||||||||||||||||||||||
| PO Rank: | 60 | ||||||||||||||||||||||||||||
| PO Ranking Note: | Could be a large data set, but not likely to need regular updating in bulk | ||||||||||||||||||||||||||||
| Rank: Chalmers (Impl Aut 2019): | R4 | ||||||||||||||||||||||||||||
| Rank: Chicago (MVP Sum 2020): | R3 | ||||||||||||||||||||||||||||
| Rank: Cornell (Full Sum 2021): | R3 | ||||||||||||||||||||||||||||
| Rank: Duke (Full Sum 2021): | R4 | ||||||||||||||||||||||||||||
| Rank: 5Colleges (Full Jul 2021): | R4 | ||||||||||||||||||||||||||||
| Rank: GBV (MVP Sum 2020): | R2 | ||||||||||||||||||||||||||||
| Rank: U of AL (MVP Oct 2020): | R5 | ||||||||||||||||||||||||||||
| Description |
|
Current situation or problem: In order to facilitate migrations in a timely and efficient manner, the Organizations Storage module needs to have batch APIs. POSTing, PUTting and DELETEing records one HTTP request and database commit at a time is unusably slow for large data sets. In scope:
Out of scope: Batch APIs for addresses, phone number, urls and categories are not required. The anticipated order of magnitude for these record sets is not sufficient to require batch handling, and they appear to be deprecated in their individual APIs anyway. Use case(s):
Comments: In order for these APIs to be effective, they need to bypass the business logic and go directly to the storage module. Any BL-level logic will need to be accounted for by the user; documentation should reflect this. |