Media type versioning in Rest API - Time & Space Complexity

Time Complexity: Media type versioning

O(n)

Understanding Time Complexity

When using media type versioning in REST APIs, it's important to understand how the server handles requests with different versions.

We want to know how the processing time changes as the number of versions or requests grows.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

GET /api/resource HTTP/1.1
Accept: application/vnd.example.v1+json

// Server checks the Accept header
switch (version) {
  case 'v1': return dataV1;
  case 'v2': return dataV2;
  default: return error;
}

This code checks the version requested in the Accept header and returns the matching data format.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Checking the version string against known versions.
• How many times: Once per request, with a small fixed number of versions to check.

How Execution Grows With Input

As the number of requests grows, the server checks the version once per request.

Input Size (n)	Approx. Operations
10 requests	10 version checks
100 requests	100 version checks
1000 requests	1000 version checks

Pattern observation: The work grows directly with the number of requests, but each check is simple and fixed.

Final Time Complexity

Time Complexity: O(n)

This means the time to handle requests grows linearly with the number of requests.

Common Mistake

[X] Wrong: "Checking the version header takes longer as more versions exist because it loops through all versions."

[OK] Correct: Usually, the server uses a simple switch or map lookup, so checking a version is a quick fixed step, not a loop over all versions.

Interview Connect

Understanding how version checks scale helps you explain API design choices clearly and shows you can think about performance in real systems.

Self-Check

"What if the server supported hundreds of versions and checked them by searching a list? How would the time complexity change?"

Practice

1. What is the main purpose of using media type versioning in REST APIs?

easy

A. To allow clients to specify API versions via custom content types

B. To encrypt API data for security

C. To speed up API response times

D. To change the API URL structure frequently

Solution

1. Step 1: Understand media type versioning concept

   Media type versioning lets clients request specific API versions by setting custom content types in headers.

2. Step 2: Identify the main purpose

   This approach helps keep APIs backward compatible by allowing multiple versions to coexist.

3. Final Answer:

   To allow clients to specify API versions via custom content types -> Option A

4. Quick Check:

   Media type versioning = clients specify versions [OK]

Hint: Remember: version info goes in content type headers [OK]

Common Mistakes:

• Confusing versioning with encryption
• Thinking URL changes are required
• Assuming it improves speed directly

2. Which HTTP header is commonly used by clients to specify the API version in media type versioning?

easy

A. Content-Type

B. Accept

C. Authorization

D. User-Agent

Solution

1. Step 1: Identify header for version negotiation

   The client uses the Accept header to tell the server which media type and version it wants.

2. Step 2: Differentiate from other headers

   Content-Type is for request body format, Authorization is for credentials, and User-Agent identifies the client software.

3. Final Answer:

   Accept -> Option B

4. Quick Check:

   Version in Accept header [OK]

Hint: Accept header tells server what version client wants [OK]

Common Mistakes:

• Using Content-Type instead of Accept for versioning
• Confusing Authorization with version info
• Thinking User-Agent controls version

3. Given this HTTP Accept header:
Accept: application/vnd.example.v2+json
What version of the API is the client requesting?

medium

A. Version 3

B. Version 1

C. Version 2

D. No version specified

Solution

1. Step 1: Parse the media type string

   The media type is application/vnd.example.v2+json. The .v2 part indicates version 2.

2. Step 2: Confirm version number meaning

   The v2 suffix is a common pattern to specify API version 2 in media type versioning.

3. Final Answer:

   Version 2 -> Option C

4. Quick Check:

   v2 in media type means version 2 [OK]

Hint: Look for .vX in media type for version number [OK]

Common Mistakes:

• Ignoring the .v2 and picking version 1
• Confusing +json suffix as version
• Assuming no version if not in URL

4. A client sends this header:
Accept: application/vnd.example.v1+json
But the server responds with version 2 data. What is the likely cause?

medium

A. Accept header syntax is invalid

B. Client sent wrong Content-Type header

C. Server does not support version 2

D. Server ignores Accept header and defaults to latest version

Solution

1. Step 1: Analyze client request and server response

   The client requests version 1 via Accept header, but server returns version 2 data.

2. Step 2: Identify server behavior

   This usually means the server ignores the Accept header and serves the latest version by default.

3. Final Answer:

   Server ignores Accept header and defaults to latest version -> Option D

4. Quick Check:

   Server ignoring Accept header causes version mismatch [OK]

Hint: Mismatch means server likely ignores Accept header [OK]

Common Mistakes:

• Blaming client Content-Type instead of Accept
• Assuming Accept header syntax error without checking
• Thinking server lacks version 2 support

5. You want to support two API versions simultaneously using media type versioning. Which server behavior best supports this?

hard

A. Parse the Accept header and return data matching the requested version

B. Ignore Accept header and always return version 2 data

C. Use URL path versioning instead of media type versioning

D. Return an error if Accept header version is not latest

Solution

1. Step 1: Understand requirement for simultaneous version support

   To support multiple versions, the server must detect which version the client wants.

2. Step 2: Identify correct server behavior

   Parsing the Accept header and returning matching version data allows backward compatibility and coexistence.

3. Final Answer:

   Parse the Accept header and return data matching the requested version -> Option A

4. Quick Check:

   Server parses Accept header to serve requested version [OK]

Hint: Server must read Accept header to serve correct version [OK]

Common Mistakes:

• Ignoring Accept header and forcing one version
• Switching to URL versioning instead of media type
• Returning errors instead of supporting old versions