Resource expansion (embed related data) in Rest API - Time & Space Complexity

Time Complexity: Resource expansion (embed related data)

O(n)

Understanding Time Complexity

When a REST API expands resources to include related data, it fetches more information in one go.

We want to know how this extra fetching affects the time it takes to get the data.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

GET /orders?expand=customer,items

// The API fetches orders, and for each order, it also fetches the related customer and items data.

This code fetches a list of orders and expands each order with its related customer and items details.

Identify Repeating Operations

• Primary operation: For each order, fetching related customer and items data.
• How many times: Once per order in the list.

How Execution Grows With Input

As the number of orders grows, the API does more work fetching related data for each order.

Input Size (n orders)	Approx. Operations
10	Fetch 10 orders + 10 customers + 10 items sets
100	Fetch 100 orders + 100 customers + 100 items sets
1000	Fetch 1000 orders + 1000 customers + 1000 items sets

Pattern observation: The work grows roughly in direct proportion to the number of orders.

Final Time Complexity

Time Complexity: O(n)

This means the time to get all data grows linearly with the number of orders requested.

Common Mistake

[X] Wrong: "Expanding related data only adds a small fixed cost regardless of how many orders there are."

[OK] Correct: Each order adds extra fetches for its related data, so the cost grows with the number of orders, not fixed.

Interview Connect

Understanding how expanding related data affects performance helps you design APIs that stay fast as data grows.

Self-Check

What if the API also expanded nested related data, like each item's supplier? How would the time complexity change?

Practice

1. What is the main purpose of using the expand parameter in a REST API request?

easy

A. To delete related resources automatically

B. To include related resource data within the main resource response

C. To paginate the results of the API response

D. To filter the main resource by specific fields

Solution

1. Step 1: Understand the expand parameter role

   The expand parameter is used to include related or nested resource data inside the main resource response.

2. Step 2: Compare with other options

   Filtering, pagination, and deletion are different API features and not related to embedding data.

3. Final Answer:

   To include related resource data within the main resource response -> Option B

4. Quick Check:

   Expand = embed related data [OK]

Hint: Expand means embed related data inside main response [OK]

Common Mistakes:

• Confusing expand with filtering or pagination
• Thinking expand deletes data
• Assuming expand changes data instead of embedding

2. Which of the following is the correct syntax to expand the 'author' field in a REST API GET request URL?

easy

A. /posts?expand=author

B. /posts?embed=author

C. /posts?include=author

D. /posts?fields=author

Solution

1. Step 1: Identify the standard parameter for resource expansion

   The common parameter to embed related data is expand.

2. Step 2: Check the URL syntax

   The correct syntax uses ?expand=author to embed the author data inside posts.

3. Final Answer:

   /posts?expand=author -> Option A

4. Quick Check:

   Use expand=field to embed [OK]

Hint: Use ?expand=resourceName to embed related data [OK]

Common Mistakes:

• Using embed or include instead of expand
• Using fields which filters fields, not expands
• Missing the question mark before parameters

3. Given the API endpoint /orders?expand=customer, what will the response include?

medium

A. A list of customers unrelated to orders

B. Only order details without customer info

C. Only customer information without orders

D. Order details with embedded customer information

Solution

1. Step 1: Analyze the expand parameter usage

   The parameter expand=customer tells the API to include customer data inside each order.

2. Step 2: Understand the response content

   The response will contain order details plus the related customer information embedded.

3. Final Answer:

   Order details with embedded customer information -> Option D

4. Quick Check:

   Expand=customer means embed customer data [OK]

Hint: Expand embeds related resource data inside main response [OK]

Common Mistakes:

• Expecting only orders without customer info
• Thinking expand replaces main resource
• Confusing expand with filtering or unrelated data

4. You tried to expand the 'comments' field with /posts?expand=comments but the API returns an error. What is the most likely cause?

medium

A. The 'comments' field is not a valid expandable resource

B. The API requires POST method for expansion

C. The expand parameter should be 'include' instead

D. The URL is missing a trailing slash

Solution

1. Step 1: Check if 'comments' is expandable

   Not all fields can be expanded; the API must support expanding 'comments'.

2. Step 2: Verify HTTP method and parameter correctness

   Expansion usually works with GET and uses 'expand', so POST or 'include' are unlikely causes.

3. Step 3: URL format check

   Missing trailing slash usually does not cause expansion errors.

4. Final Answer:

   The 'comments' field is not a valid expandable resource -> Option A

5. Quick Check:

   Expandable fields must be supported by API [OK]

Hint: Check if field supports expand before using it [OK]

Common Mistakes:

• Using wrong HTTP method for expansion
• Confusing expand with include parameter
• Assuming all fields are expandable

5. You want to get a list of invoices with embedded customer and payment details in one API call. Which URL correctly uses resource expansion for both related resources?

hard

A. /invoices?embed=customer,payment

B. /invoices?expand=customer&expand=payment

C. /invoices?expand=customer,payment

D. /invoices?expand=customer;payment

Solution

1. Step 1: Understand how to expand multiple resources

   Multiple expansions are usually comma-separated in a single expand parameter.

2. Step 2: Evaluate each option's syntax

   /invoices?expand=customer,payment uses comma-separated values correctly. /invoices?expand=customer&expand=payment repeats the parameter which is often unsupported. /invoices?embed=customer,payment uses 'embed' which is incorrect. /invoices?expand=customer;payment uses semicolon which is not standard.

3. Final Answer:

   /invoices?expand=customer,payment -> Option C

4. Quick Check:

   Multiple expands separated by commas [OK]

Hint: Use commas to expand multiple resources in one parameter [OK]

Common Mistakes:

• Repeating expand parameter multiple times
• Using embed instead of expand
• Separating resources with semicolons