Graceful degradation in Rest API

Introduction

Graceful degradation helps your API keep working even if some parts fail. It avoids total crashes and gives users useful responses.

When a part of your API depends on an external service that might be slow or down.

When you want to provide partial data instead of failing completely.

When you want to show a simple message if a feature is temporarily unavailable.

When you want to keep your API responsive during high traffic or errors.

When you want to improve user experience by handling errors smoothly.

Syntax

Rest API

try {
  // call external service or risky code
  return full response;
} catch (error) {
  // fallback response or partial data
  return degraded response;
}

Use try-catch or error handling to detect failures.

Return simpler or partial data instead of full failure.

Examples

This example tries to get data from an external API. If it fails, it returns a simple message instead of an error.

Rest API

try {
  const data = await fetchExternalAPI();
  return { status: 200, data };
} catch {
  return { status: 200, data: { message: 'Partial data available' } };
}

If fetching orders fails, the API still returns user info with an empty orders list.

Rest API

try {
  const user = await getUserFromDB();
  const orders = await getOrdersFromDB();
  return { user, orders };
} catch {
  return { user: null, orders: [] };
}

Sample Program

This simple REST API tries to get data from a service. If the service fails, it returns partial data instead of an error. This keeps the API working smoothly.

Rest API

import express from 'express';
const app = express();

// Simulate external service call
async function fetchExternalService() {
  if (Math.random() < 0.5) {
    throw new Error('Service down');
  }
  return { info: 'Full data from service' };
}

app.get('/data', async (req, res) => {
  try {
    const data = await fetchExternalService();
    res.status(200).json({ success: true, data });
  } catch (error) {
    // Graceful degradation: return partial data
    res.status(200).json({ success: true, data: { info: 'Partial data due to service issue' } });
  }
});

app.listen(3000, () => console.log('API running on http://localhost:3000'));

Important Notes

Always return a success status if you provide useful fallback data.

Log errors internally to fix issues later, but don't expose them to users.

Test your graceful degradation by simulating failures.

Summary

Graceful degradation keeps your API working even when parts fail.

It returns simpler or partial data instead of errors.

This improves user experience and reliability.

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