Graceful degradation in Rest API - Time & Space Complexity

Time Complexity: Graceful degradation

O(1)

Understanding Time Complexity

When building REST APIs, graceful degradation means the system still works even if some parts fail.

We want to see how the time cost changes when handling fallback or error cases.

Scenario Under Consideration

Analyze the time complexity of the following REST API handler with graceful degradation.

async function fetchUserData(userId) {
  try {
    const profile = await fetch(`/api/profile/${userId}`);
    if (!profile.ok) throw new Error('Profile error');
    const data = await profile.json();
    return data;
  } catch {
    return { name: 'Guest', status: 'Limited data' };
  }
}

This code tries to get user profile data. If it fails, it returns default limited data instead.

Identify Repeating Operations

Look for repeated or costly steps in the code.

• Primary operation: One network request to fetch user profile.
• How many times: Exactly once per function call, no loops or recursion.

How Execution Grows With Input

The function makes one request regardless of input size.

Input Size (n)	Approx. Operations
10	1 request
100	1 request
1000	1 request

Pattern observation: The number of operations stays the same no matter how big the input is.

Final Time Complexity

Time Complexity: O(1)

This means the time to run the function does not grow with input size; it stays constant.

Common Mistake

[X] Wrong: "The time grows with the size of the userId or data returned."

[OK] Correct: The function only makes one request and handles one response, so time depends on that single call, not input size.

Interview Connect

Understanding how graceful degradation affects time complexity helps you design APIs that stay efficient even when handling errors or fallback data.

Self-Check

"What if the function made multiple fallback requests in sequence? How would the time complexity change?"

Practice

1. What is the main goal of graceful degradation in REST APIs?

easy

A. To keep the API working even if some parts fail

B. To stop the API immediately when an error occurs

C. To ignore all errors and continue without response

D. To make the API faster by skipping error checks

Solution

1. Step 1: Understand graceful degradation purpose

   Graceful degradation means the system still works even if some parts fail.

2. Step 2: Compare options with this meaning

   Only To keep the API working even if some parts fail matches this idea by keeping the API working despite failures.

3. Final Answer:

   To keep the API working even if some parts fail -> Option A

4. Quick Check:

   Graceful degradation = keep working despite failure [OK]

Hint: Graceful degradation means continue working despite errors [OK]

Common Mistakes:

• Thinking it stops the API on error
• Assuming errors are ignored without response
• Confusing with performance optimization

2. Which of the following is the correct way to handle errors for graceful degradation in a REST API response (in pseudocode)?

easy

A. ignore errors and return nothing

B. return data; if error then stop

C. try { return data } catch { return fallbackData }

D. throw error without handling

Solution

1. Step 1: Identify error handling syntax

   Graceful degradation uses try-catch to handle errors and provide fallback data.

2. Step 2: Match options to this pattern

   try { return data } catch { return fallbackData } shows try-catch with fallback, others either stop or ignore errors.

3. Final Answer:

   try { return data } catch { return fallbackData } -> Option C

4. Quick Check:

   Use try-catch with fallback for graceful degradation [OK]

Hint: Use try-catch to return fallback on error [OK]

Common Mistakes:

• Not catching errors properly
• Stopping API on first error
• Ignoring fallback responses

3. Consider this pseudocode for a REST API endpoint:

function getUserData() {
  try {
    return fetchUserFromDB();
  } catch (error) {
    return { name: "Guest", id: 0 };
  }
}

What will getUserData() return if the database fetch fails?

medium

A. An error message

B. Nothing, the function crashes

C. Null

D. A default user object with name 'Guest' and id 0

Solution

1. Step 1: Analyze try block behavior

   If fetchUserFromDB() works, it returns user data.

2. Step 2: Analyze catch block fallback

   If an error occurs, catch returns default user object with name 'Guest' and id 0.

3. Final Answer:

   A default user object with name 'Guest' and id 0 -> Option D

4. Quick Check:

   Error fallback returns default user object [OK]

Hint: Catch returns default object on failure [OK]

Common Mistakes:

• Assuming function crashes on error
• Expecting null instead of fallback object
• Thinking error message is returned

4. This REST API code snippet is meant to provide graceful degradation but has a bug:

function getData() {
  try {
    return fetchData();
  } catch (error) {
    fallbackData;
  }
}

What is the problem?

medium

A. The try block is missing

B. The fallback data is not returned in the catch block

C. The function does not catch errors

D. The function returns twice

Solution

1. Step 1: Check catch block code

   The catch block has fallbackData; but does not return it.

2. Step 2: Understand function return behavior

   Without return, the function returns undefined on error, breaking graceful degradation.

3. Final Answer:

   The fallback data is not returned in the catch block -> Option B

4. Quick Check:

   Catch must return fallback data for graceful degradation [OK]

Hint: Always return fallback data inside catch block [OK]

Common Mistakes:

• Forgetting to return fallback data
• Misplacing try-catch blocks
• Assuming catch auto-returns value

5. You have a REST API that fetches user profile and user posts separately. To apply graceful degradation, which approach is best?

hard

A. If fetching posts fails, return profile with empty posts list

B. If fetching posts fails, return error and no profile

C. Stop API if either profile or posts fail

D. Ignore profile and only return posts

Solution

1. Step 1: Understand graceful degradation in multi-part fetch

   It means returning partial data if one part fails, not stopping all.

2. Step 2: Evaluate options for partial fallback

   If fetching posts fails, return profile with empty posts list returns profile and empty posts if posts fail, matching graceful degradation.

3. Final Answer:

   If fetching posts fails, return profile with empty posts list -> Option A

4. Quick Check:

   Partial data returned on failure = graceful degradation [OK]

Hint: Return partial data with fallback for failed parts [OK]

Common Mistakes:

• Stopping API on any failure
• Returning no data if one part fails
• Ignoring fallback for partial data