200 OK and 201 Created in Rest API - Time & Space Complexity
When working with REST APIs, it is helpful to understand how the server handles requests and how long it takes to respond.
We want to see how the response time grows when the server sends back different status codes like 200 OK or 201 Created.
Analyze the time complexity of the following REST API response handling.
POST /items
Request body: {"name": "item1"}
// Server processes the request
if (item created successfully) {
return 201 Created with new item data
} else {
return 200 OK with existing item data
}
This code snippet shows how the server decides to respond with either 201 Created or 200 OK after processing a POST request.
Look for repeated steps or loops in the server processing.
- Primary operation: Checking if the item exists or creating a new item.
- How many times: Usually once per request, no loops involved.
The server handles each request individually, so the time depends mostly on the database check or insert.
| Input Size (n) | Approx. Operations |
|---|---|
| 10 | About 10 checks or inserts |
| 100 | About 100 checks or inserts |
| 1000 | About 1000 checks or inserts |
Pattern observation: The work grows linearly with the number of requests, but each request itself is handled in constant time.
Time Complexity: O(1)
This means each request is handled in constant time, regardless of the data size.
[X] Wrong: "The server takes longer to respond with 201 Created than 200 OK because it creates new data."
[OK] Correct: Both responses usually take similar time since creation and checking are simple operations done once per request.
Understanding how API responses work and their time cost helps you explain backend behavior clearly and confidently in interviews.
"What if the server had to check multiple related tables before responding? How would the time complexity change?"