Why WebSockets enable real-time communication in FastAPI - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

How do WebSockets maintain a connection?

In FastAPI, WebSockets allow continuous communication between client and server. How do WebSockets keep this connection open?

A They use HTTP polling to check for new messages every few seconds.

B They repeatedly open and close HTTP connections for each message sent.

C They send messages only when the client refreshes the page.

D They open a single TCP connection that stays open for ongoing message exchange.

💡 Hint

Think about a phone call that stays connected instead of hanging up after each sentence.

WebSockets create a single TCP connection that remains open, allowing messages to flow instantly both ways without reopening connections.

❓ component_behavior

intermediate

What happens when a FastAPI WebSocket receives a message?

Consider a FastAPI WebSocket endpoint that echoes messages back to the client. What is the expected behavior when the client sends a message?

FastAPI

from fastapi import FastAPI, WebSocket
app = FastAPI()

@app.websocket('/ws')
async def websocket_endpoint(websocket: WebSocket):
    await websocket.accept()
    data = await websocket.receive_text()
    await websocket.send_text(f'Message received: {data}')

A The server closes the connection immediately after receiving the message.

B The server accepts the connection, receives the message, and sends back a confirmation with the message content.

C The server ignores the message and sends no response.

D The server crashes because it does not handle binary messages.

💡 Hint

Look at the send_text line and what it sends back.

The server accepts the WebSocket connection, waits for a text message, then sends back a confirmation including the received message.

📝 Syntax

advanced

Identify the syntax error in this FastAPI WebSocket code

Which option contains the correct syntax for accepting a WebSocket connection and receiving a text message?

FastAPI

from fastapi import FastAPI, WebSocket
app = FastAPI()

@app.websocket('/ws')
async def websocket_endpoint(websocket: WebSocket):
    await websocket.accept()
    data = await websocket.receive_text()
    await websocket.send_text(f'Received: {data}')

A

def websocket_endpoint(websocket: WebSocket):
    await websocket.accept()
    data = await websocket.receive_text()
    await websocket.send_text(f'Received: {data}')

B

async def websocket_endpoint(websocket: WebSocket):
    websocket.accept()
    data = websocket.receive_text()
    websocket.send_text(f'Received: {data}')

C

async def websocket_endpoint(websocket: WebSocket):
    await websocket.accept()
    data = await websocket.receive_text()
    await websocket.send_text(f'Received: {data}')

D

async def websocket_endpoint(websocket: WebSocket):
    await websocket.accept
    data = await websocket.receive_text()
    await websocket.send_text(f'Received: {data}')

💡 Hint

Check for missing await keywords and function definitions.

Option C correctly uses async def and awaits all async calls. Option C misses awaits, C is not async, and D misses parentheses on accept.

❓ state_output

advanced

What is the output after multiple WebSocket messages?

Given this FastAPI WebSocket code that counts messages, what is the value of count after receiving three messages?

FastAPI

from fastapi import FastAPI, WebSocket
app = FastAPI()

@app.websocket('/ws')
async def websocket_endpoint(websocket: WebSocket):
    await websocket.accept()
    count = 0
    for _ in range(3):
        await websocket.receive_text()
        count += 1
    await websocket.send_text(f'Messages received: {count}')

A 'Messages received: 3'

B 'Messages received: 0'

C 'Messages received: 1'

D RuntimeError due to missing await in loop

💡 Hint

Count increments inside the loop for each message received.

The loop runs three times, each time receiving a message and increasing count by 1, so count is 3.

🔧 Debug

expert

Why does this FastAPI WebSocket code raise an error?

Examine this WebSocket endpoint code. Why does it raise a RuntimeError: Cannot call receive_text() after connection is closed?

FastAPI

from fastapi import FastAPI, WebSocket
app = FastAPI()

@app.websocket('/ws')
async def websocket_endpoint(websocket: WebSocket):
    await websocket.accept()
    data = await websocket.receive_text()
    await websocket.close()
    data2 = await websocket.receive_text()

A Because the code tries to receive a message after closing the WebSocket connection.

B Because the WebSocket was never accepted before receiving messages.

C Because receive_text() requires a timeout parameter.

D Because the close() method is not awaited properly.

💡 Hint

Think about what happens after closing a connection.

After calling await websocket.close(), the connection is closed. Trying to receive another message causes a RuntimeError.

Practice

1. Why do WebSockets enable real-time communication in FastAPI applications?

easy

A. Because they only send data from server to client once

B. Because they use HTTP requests repeatedly to fetch new data

C. Because they keep a constant open connection for instant two-way data exchange

D. Because they require manual page refresh to update data

Solution

1. Step 1: Understand WebSocket connection behavior

   WebSockets maintain a persistent connection allowing continuous data flow without reconnecting.

2. Step 2: Compare with HTTP request-response model

   Unlike HTTP, which closes after each request, WebSockets allow instant two-way communication.

3. Final Answer:

   Because they keep a constant open connection for instant two-way data exchange -> Option C

4. Quick Check:

   Persistent connection = real-time communication [OK]

Hint: Remember: WebSockets keep connection open for instant updates [OK]

Common Mistakes:

• Confusing WebSockets with repeated HTTP requests
• Thinking WebSockets only send data one way
• Assuming page refresh is needed for updates

2. Which of the following is the correct way to define a WebSocket route in FastAPI?

easy

A. app.websocket('/ws') async def websocket_endpoint(websocket): await websocket.accept()

B. app.get('/ws') async def websocket_endpoint(websocket): await websocket.accept()

C. app.post('/ws') def websocket_endpoint(websocket): websocket.accept()

D. app.websocket('/ws') def websocket_endpoint(): websocket.accept()

Solution

1. Step 1: Identify correct decorator and async function

   FastAPI uses @app.websocket decorator and async def for WebSocket routes.

2. Step 2: Confirm usage of await websocket.accept()

   Accepting the connection requires awaiting websocket.accept() inside async function.

3. Final Answer:

   app.websocket('/ws') async def websocket_endpoint(websocket): await websocket.accept() -> Option A

4. Quick Check:

   Use @app.websocket + async + await accept() [OK]

Hint: WebSocket routes need @app.websocket and async functions [OK]

Common Mistakes:

• Using HTTP method decorators like @app.get for WebSockets
• Forgetting async or await keywords
• Defining function without websocket parameter

3. Given this FastAPI WebSocket code snippet, what will the client receive after sending 'hello'?

from fastapi import FastAPI, WebSocket
app = FastAPI()

@app.websocket('/ws')
async def websocket_endpoint(websocket: WebSocket):
    await websocket.accept()
    data = await websocket.receive_text()
    await websocket.send_text(f'Received: {data}')

medium

A. 'hello'

B. Error: websocket not accepted

C. No response, connection closed

D. 'Received: hello'

Solution

1. Step 1: Analyze the receive and send calls

   The server waits for text, receives 'hello', then sends back 'Received: hello'.

2. Step 2: Confirm connection acceptance

   websocket.accept() is awaited, so connection is open and ready for communication.

3. Final Answer:

   'Received: hello' -> Option D

4. Quick Check:

   Server echoes with prefix 'Received:' [OK]

Hint: Look for send_text with formatted string after receive_text [OK]

Common Mistakes:

• Assuming no response is sent
• Ignoring the awaited accept() call
• Confusing received data with sent data

4. What is wrong with this FastAPI WebSocket handler code?

@app.websocket('/ws')
async def websocket_endpoint(websocket: WebSocket):
    data = await websocket.receive_text()
    await websocket.accept()
    await websocket.send_text(f'Got: {data}')

medium

A. Incorrect route decorator used

B. Calling receive_text before accepting the connection

C. Using send_text instead of send_bytes

D. Missing async keyword in function definition

Solution

1. Step 1: Check order of accept and receive calls

   WebSocket connection must be accepted before receiving data.

2. Step 2: Identify the error caused by wrong order

   Calling receive_text before accept() causes runtime error as connection is not open yet.

3. Final Answer:

   Calling receive_text before accepting the connection -> Option B

4. Quick Check:

   Accept connection before receiving data [OK]

Hint: Always await websocket.accept() before receiving messages [OK]

Common Mistakes:

• Receiving data before accepting connection
• Forgetting async keyword
• Confusing send_text with send_bytes

5. You want to build a live chat app using FastAPI WebSockets. Which approach best ensures real-time updates to all connected clients?

hard

A. Keep a list of connected WebSocket objects and broadcast messages to all

B. Send HTTP requests every second to fetch new messages

C. Open a new WebSocket connection for each message sent

D. Use a database trigger to push messages without WebSockets

Solution

1. Step 1: Understand real-time broadcast requirement

   To update all clients instantly, server must send messages to all open connections.

2. Step 2: Identify best method for broadcasting

   Maintaining a list of connected WebSocket objects allows sending messages to all clients immediately.

3. Final Answer:

   Keep a list of connected WebSocket objects and broadcast messages to all -> Option A

4. Quick Check:

   Broadcast via open WebSocket connections = real-time updates [OK]

Hint: Broadcast by storing and sending to all connected sockets [OK]

Common Mistakes:

• Using repeated HTTP polling instead of WebSockets
• Opening new connections per message wastes resources
• Relying on database triggers without WebSocket communication