Design an API Request Workspace
Design a shared workspace for composing, saving, and executing API requests.
Problem statement
For this exercise, assume a team uses one workspace to compose HTTP requests, save them in named collections, run them, inspect bounded responses, and share collections with teammates. A saved request contains a method, target URL, headers, and optional body. Running a request must leave the saved definition unchanged.
A teammate can view or edit a collection only when its owner grants that permission. The platform must reject destinations on private or loopback networks; it does not need to manage production secrets, scheduled runs, or public collection publishing.
Design the end-to-end system and explain where saved state, execution, authorization, and response delivery live.
What to build
- Create and edit request definitions inside named collections; keep saved definitions durable.
- Run one composed or saved HTTP request and show a bounded status, headers, and response body without changing the saved definition.
- Grant teammates view or edit access to a collection and enforce that permission on reads, edits, and runs.
At scale
- Assume 100,000 saved request definitions across 10,000 active teams; this makes collection indexing and ownership meaningful.
- Assume up to 10,000 simultaneous request runs with a 30-second timeout; execution isolation and backpressure matter.
- Assume a response body is retained for at most 10 minutes and capped at 10 MB; larger responses may be truncated with an explicit marker.