Multi-tenant applications in Remix - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to get the tenant ID from the request URL in a Remix loader.

Remix

export async function loader({ request }) {
  const url = new URL(request.url);
  const tenantId = url.pathname.split('/')[[1]];
  return { tenantId };
}

Drag options to blanks, or click blank then click option'

A1

B2

C3

D0

Attempts:

3 left

💡 Hint

Common Mistakes

Using index 0 which is empty string due to leading slash

Using index 2 which is usually the next segment

Using index 3 which is usually the next segment

The tenant ID is usually the first segment after the domain, which is at index 1 in the pathname split array.

2fill in blank

medium

Complete the code to create a Remix route that uses the tenant ID as a dynamic segment.

Remix

export const loader = async ({ params }) => {
  const tenantId = params.[1];
  return { tenantId };
};

Drag options to blanks, or click blank then click option'

Aslug

BuserId

CtenantId

Did

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'id' when the segment is named 'tenantId'

Using 'slug' or 'userId' which are unrelated

The dynamic segment in the route file should be named $tenantId, so the param key is 'tenantId'.

3fill in blank

hard

Fix the error in this Remix loader to correctly fetch tenant-specific data.

Remix

export async function loader({ params }) {
  const tenant = params.[1];
  const data = await fetch(`/api/data?tenant=${tenant}`);
  return data.json();
}

Drag options to blanks, or click blank then click option'

Aid

BtenantId

Ctenant

Duser

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'tenant' instead of 'tenantId'

Using 'id' or 'user' which are unrelated

The param key must match the dynamic segment name, which is 'tenantId' in this case.

4fill in blank

hard

Fill both blanks to create a tenant-aware API route handler in Remix.

Remix

export async function loader({ request, params }) {
  const tenantId = params.[1];
  const url = new URL(request.url);
  const resource = url.searchParams.get('[2]');
  return fetch(`https://api.example.com/${tenantId}/${resource}`);
}

Drag options to blanks, or click blank then click option'

AtenantId

Bresource

Cid

Ddata

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'id' instead of 'tenantId' for params

Using 'data' instead of 'resource' for query param

The param key is 'tenantId' and the query parameter to get is 'resource' to build the API URL correctly.

5fill in blank

hard

Fill all three blanks to implement tenant-specific context in a Remix root component.

Remix

import { createContext, useContext } from 'react';

const TenantContext = createContext(null);

export function TenantProvider({ children, [1] }) {
  return <TenantContext.Provider value=[2]>[3]</TenantContext.Provider>;
}

export function useTenant() {
  return useContext(TenantContext);
}

Drag options to blanks, or click blank then click option'

AtenantId

Cchildren

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing 'children' and 'tenantId' props

Not passing the tenant ID as context value

The provider receives tenantId as a prop, passes it as the context value, and renders children inside.

Practice

1. What is the main purpose of a multi-tenant application in Remix Framework?

easy

A. To run multiple Remix apps on different servers

B. To create multiple copies of the same app for each user

C. To allow users to share the same data across all tenants

D. To serve multiple user groups with separate data using one codebase

Solution

1. Step 1: Understand multi-tenant concept

   Multi-tenant apps use one codebase but keep data separate for each user group or tenant.

2. Step 2: Identify Remix multi-tenant goal

   Remix apps handle requests to serve tenant-specific data without duplicating code.

3. Final Answer:

   To serve multiple user groups with separate data using one codebase -> Option D

4. Quick Check:

   Multi-tenant = shared code, separate data [OK]

Hint: Multi-tenant means one app, many separate user groups [OK]

Common Mistakes:

• Thinking each tenant needs a separate app
• Assuming tenants share the same data
• Confusing multi-tenant with multi-instance

2. Which Remix loader function signature correctly receives the tenant info from the request?

easy

A. export async function loader({ request }) { /* use request to get tenant */ }

B. export async function loader(request) { /* tenant info here */ }

C. export async function loader(context) { /* tenant in context */ }

D. export async function loader() { /* no params for tenant */ }

Solution

1. Step 1: Recall Remix loader signature

   Remix loaders receive an object with a request property: loader({ request }).

2. Step 2: Identify correct usage for tenant extraction

   Tenant info is extracted from the request object, so the loader must accept { request }.

3. Final Answer:

   export async function loader({ request }) { /* use request to get tenant */ } -> Option A

4. Quick Check:

   Loader({ request }) is correct signature [OK]

Hint: Loader always gets an object with request property [OK]

Common Mistakes:

• Using request as a direct parameter instead of inside an object
• Expecting tenant info in a 'context' parameter
• Defining loader with no parameters

3. Given this loader code snippet in a multi-tenant Remix app, what will be returned if the request URL is 'https://app.com/tenantA/dashboard'?

export async function loader({ request }) {
  const url = new URL(request.url);
  const tenant = url.pathname.split('/')[1];
  return { tenant };
}

medium

A. { tenant: 'tenantA' }

B. { tenant: 'dashboard' }

C. { tenant: '' }

D. Throws an error

Solution

1. Step 1: Parse the URL pathname

   The pathname is '/tenantA/dashboard'. Splitting by '/' gives ['', 'tenantA', 'dashboard'].

2. Step 2: Extract tenant from split array

   The tenant is at index 1, which is 'tenantA'.

3. Final Answer:

   { tenant: 'tenantA' } -> Option A

4. Quick Check:

   Split pathname[1] = tenant name [OK]

Hint: Split URL path by '/' and pick index 1 for tenant [OK]

Common Mistakes:

• Picking index 2 instead of 1 for tenant
• Not accounting for leading slash causing empty string at index 0
• Assuming tenant is query parameter

4. Identify the bug in this Remix loader for multi-tenant data fetching:

export async function loader({ request }) {
  const url = new URL(request.url);
  const tenant = url.pathname.split('/')[2];
  if (!tenant) throw new Error('Tenant missing');
  return { tenant };
}

medium

A. Loader must not return an object

B. Tenant index should be 1, not 2

C. Error should be returned, not thrown

D. Missing await keyword before new URL()

Solution

1. Step 1: Analyze pathname splitting

   Pathname split by '/' results in ['', tenant, ...]. Tenant is at index 1, not 2.

2. Step 2: Understand error condition

   If tenant is at index 2, it will often be undefined, causing error even when tenant exists.

3. Final Answer:

   Tenant index should be 1, not 2 -> Option B

4. Quick Check:

   Tenant = pathname.split('/')[1] [OK]

Hint: Tenant is always at index 1 after splitting pathname [OK]

Common Mistakes:

• Using wrong index for tenant extraction
• Confusing async usage with URL constructor
• Throwing error instead of handling gracefully

5. How can you ensure tenant data isolation in a Remix multi-tenant app when fetching data in the loader?

hard

A. Store tenant data in a global variable accessible to all requests

B. Fetch all tenants' data and filter on the client side

C. Use the tenant identifier from the request to query only that tenant's data

D. Use a single database table without tenant filtering

Solution

1. Step 1: Understand tenant data isolation

   Each tenant must only access their own data to keep data private and secure.

2. Step 2: Apply tenant filtering in loader

   Extract tenant ID from request and query database filtering by that tenant only.

3. Final Answer:

   Use the tenant identifier from the request to query only that tenant's data -> Option C

4. Quick Check:

   Filter data by tenant in loader for isolation [OK]

Hint: Filter data by tenant ID in loader, not client side [OK]

Common Mistakes:

• Fetching all data and filtering later (inefficient and unsafe)
• Using global variables for tenant data
• Ignoring tenant filtering in queries