Optional and nullable fields in FastAPI - Performance & Optimization

Performance: Optional and nullable fields

MEDIUM IMPACT

This affects the API response size and validation speed, impacting initial response time and user experience.

Defining API request/response models with optional and nullable fields

FastAPI

from typing import Optional
from pydantic import BaseModel

class User(BaseModel):
    name: str
    age: Optional[int] = None  # only optional if truly needed
    email: str

Only mark fields optional or nullable when necessary, reducing payload and validation overhead.

📈 Performance GainSmaller JSON payload and faster validation, improving response time by milliseconds.

Defining API request/response models with optional and nullable fields

FastAPI

from typing import Optional
from pydantic import BaseModel

class User(BaseModel):
    name: Optional[str] = None
    age: Optional[int] = None
    email: Optional[str] = None

Using many optional fields increases payload size and validation complexity even when fields are unused.

📉 Performance CostIncreases JSON size and validation time, blocking response for extra milliseconds per request.

Performance Comparison

Pattern	Validation Cost	Payload Size	Response Time Impact	Verdict
Many optional/nullable fields	High (validates many fields)	Large (includes nulls)	Slower (blocks response)	[X] Bad
Minimal optional/nullable fields	Low (validates fewer fields)	Small (only needed data)	Faster (quicker response)	[OK] Good

Rendering Pipeline

Optional and nullable fields affect the server's JSON serialization and validation before sending data to the client, impacting the critical rendering path by delaying content availability.

→Validation

→Serialization

→Network Transfer

⚠️ BottleneckSerialization and validation increase CPU time and payload size, delaying LCP.

Core Web Vital Affected

LCP

This affects the API response size and validation speed, impacting initial response time and user experience.

Optimization Tips

1Avoid unnecessary optional or nullable fields to keep payloads small.

2Exclude unset optional fields from JSON responses to reduce size.

3Validate only required fields to speed up API response time.

Performance Quiz - 3 Questions

How do many optional and nullable fields in FastAPI models affect API performance?

A They reduce payload size and speed up validation.

B They have no impact on performance.

C They increase payload size and validation time, slowing response.

D They only affect frontend rendering, not API speed.

DevTools: Network

How to check: Open DevTools > Network tab > Inspect API response size and timing for requests with optional fields.

What to look for: Look for large JSON payloads and longer response times indicating heavy optional/nullable field usage.

Practice

1. In FastAPI, what does it mean when a field is declared as Optional[str] in a request model?

easy

A. The field is required and cannot be None.

B. The field must always be provided with a string value.

C. The field can only be an empty string but not None.

D. The field can be omitted or set to None in the request.

Solution

1. Step 1: Understand Optional type in FastAPI

   Optional[str] means the field can be missing or have a value of type str or None.

2. Step 2: Interpret the meaning for API requests

   This allows clients to omit the field or explicitly send null (None) as its value.

3. Final Answer:

   The field can be omitted or set to None in the request. -> Option D

4. Quick Check:

   Optional[str] = omitted or None [OK]

Hint: Optional means field can be missing or None [OK]

Common Mistakes:

• Thinking Optional means field is always required
• Confusing Optional with default values
• Assuming Optional forbids None

2. Which of the following is the correct way to declare a nullable string field in a FastAPI Pydantic model?

easy

A. name: Optional[str] = None

B. name: str | None = None

C. name: str = None

D. name: str?

Solution

1. Step 1: Recall Pydantic syntax for optional and nullable fields

   To allow a field to be nullable and optional, use Optional[str] with a default None.

2. Step 2: Check each option

   A is invalid because just assigning None to str without Optional is not correct. B is valid Python 3.10+ syntax but C is the recommended explicit way in FastAPI. D is invalid syntax.

3. Final Answer:

   name: Optional[str] = None -> Option A

4. Quick Check:

   Nullable string = Optional[str] = None [OK]

Hint: Use Optional[type] with = None for nullable fields [OK]

Common Mistakes:

• Using just type with = None without Optional
• Using invalid syntax like str?
• Confusing Optional with just default values

3. Given this FastAPI model:

from typing import Optional
from pydantic import BaseModel

class User(BaseModel):
    name: str
    nickname: Optional[str] = None

user = User(name='Alice')

What will be the value of user.nickname?

medium

A. '' (empty string)

B. 'Alice'

C. None

D. Raises an error

Solution

1. Step 1: Analyze the model fields and defaults

   The nickname field is Optional[str] with a default of None, so if not provided, it defaults to None.

2. Step 2: Check the instance creation

   When creating user with only name='Alice', nickname is not set, so it uses the default None.

3. Final Answer:

   None -> Option C

4. Quick Check:

   Optional field missing = None [OK]

Hint: Missing optional field defaults to None [OK]

Common Mistakes:

• Assuming nickname defaults to empty string
• Thinking nickname copies name value
• Expecting an error for missing optional field

4. What is wrong with this FastAPI model declaration?

from typing import Optional
from pydantic import BaseModel

class Item(BaseModel):
    description: Optional[str]

medium

A. Optional[str] is not allowed in Pydantic models.

B. Missing default value for Optional field causes validation error.

C. Field description must be declared as str, not Optional[str].

D. No import for Optional is present.

Solution

1. Step 1: Understand Optional fields in Pydantic

   Optional means the field can be None or missing, but Pydantic requires a default value for optional fields.

2. Step 2: Check the model declaration

   The field description is Optional[str] but has no default value, so Pydantic will expect it to be provided and raise an error if missing.

3. Final Answer:

   Missing default value for Optional field causes validation error. -> Option B

4. Quick Check:

   Optional fields need default values [OK]

Hint: Optional fields must have default values [OK]

Common Mistakes:

• Omitting default None for Optional fields
• Thinking Optional alone makes field optional
• Ignoring Pydantic validation rules

5. You want to create a FastAPI model where the field email can be omitted, but if present, it can be set to null explicitly. Which is the best way to declare this field?

hard

A. email: Optional[str] = None

B. email: str = None

C. email: str | None

D. email: Optional[str]

Solution

1. Step 1: Understand requirements for the field

   The field must be optional (can be omitted) and nullable (can be None explicitly).

2. Step 2: Evaluate each declaration

   B lacks Optional and default None, so it is not optional. C lacks default None, so field is required. D lacks default None, so field is required. A uses Optional[str] with default None, making it optional and nullable.

3. Final Answer:

   email: Optional[str] = None -> Option A

4. Quick Check:

   Optional with default None = optional and nullable [OK]

Hint: Use Optional[type] with = None for optional nullable fields [OK]

Common Mistakes:

• Forgetting to assign default None
• Using union without default value
• Assuming Optional alone makes field optional