RPC vs direct API calls in RabbitMQ - Quick Revision & Key Differences

Recall & Review

beginner

What does RPC stand for in the context of RabbitMQ?

RPC stands for Remote Procedure Call. It allows a program to request a service from a program located on another computer in a network.

beginner

How does direct API call communication differ from RPC?

Direct API calls involve a client sending a request directly to a server's endpoint and waiting for a response, usually over HTTP. RPC uses messaging queues to send requests and receive responses asynchronously.

intermediate

What is a key advantage of using RPC with RabbitMQ over direct API calls?

RPC with RabbitMQ decouples the client and server via the message broker, enabling better scalability and fault tolerance.

intermediate

What is a common use case for direct API calls instead of RPC?

Direct API calls are often used when immediate, synchronous responses are needed, such as fetching data from a web service where the client waits for the response before continuing.

beginner

In RabbitMQ RPC, what role does the message queue play?

The message queue acts as a middleman that holds the request message until the server processes it and sends back a response message to the client.

What is the main difference between RPC and direct API calls?

A RPC cannot be used over a network.

B RPC uses messaging queues and can be asynchronous; direct API calls are usually synchronous.

C Direct API calls use message queues; RPC uses HTTP requests.

D RPC is always faster than direct API calls.

RPC uses messaging queues allowing asynchronous communication, while direct API calls are typically synchronous HTTP requests.

Which scenario is best suited for direct API calls?

A When the client needs an immediate response before continuing.

B When the client wants to send messages without waiting for a response.

C When using RabbitMQ for asynchronous processing.

D When the server is offline.

Direct API calls are synchronous and best when the client needs an immediate response.

In RabbitMQ RPC, what happens after the client sends a request message?

A The server ignores the message.

B The client immediately receives a response without waiting.

C The client sends a direct HTTP request.

D The message is placed in a queue and the client waits for a response message.

The request message is placed in a queue; the client waits asynchronously for the server's response.

Which of the following is NOT an advantage of using RPC with RabbitMQ?

A Allows asynchronous communication.

B Decouples client and server.

C Requires the client to wait synchronously for the response.

D Improves scalability by using message queues.

RPC with RabbitMQ uses asynchronous messaging, but the RPC pattern requires the client to wait synchronously for the response.

What protocol do direct API calls commonly use?

A HTTP/HTTPS

B AMQP

C FTP

D SMTP

Direct API calls commonly use HTTP or HTTPS protocols.

Explain the main differences between RPC using RabbitMQ and direct API calls.

Think about how messages are sent and how the client waits for responses.

Describe a situation where you would prefer to use direct API calls over RPC.

Consider when waiting for a quick answer is important.

Practice

1. What is a key difference between RabbitMQ RPC and direct API calls?

easy

A. RPC uses message queues to communicate asynchronously, while direct API calls use HTTP requests synchronously.

B. RPC requires a web browser, but direct API calls do not.

C. Direct API calls always use message queues, but RPC uses HTTP.

D. RPC is only used for database queries, direct API calls are for UI updates.

Solution

1. Step 1: Understand communication methods

   RPC in RabbitMQ uses message queues to send and receive messages asynchronously between services.

2. Step 2: Compare with direct API calls

   Direct API calls typically use HTTP requests for immediate, synchronous communication between client and server.

3. Final Answer:

   RPC uses message queues to communicate asynchronously, while direct API calls use HTTP requests synchronously. -> Option A

4. Quick Check:

   RPC = asynchronous messaging, API calls = synchronous HTTP [OK]

Hint: RPC = queues and async; API calls = HTTP and sync [OK]

Common Mistakes:

• Confusing RPC with HTTP usage
• Thinking RPC requires a browser
• Assuming direct API uses queues

2. Which of the following is the correct RabbitMQ RPC client call pattern?

easy

A. Directly call function in remote service without messaging

B. Send HTTP GET request to server endpoint

C. Send message to queue, wait for reply on callback queue

D. Open TCP socket and stream data continuously

Solution

1. Step 1: Identify RabbitMQ RPC client behavior

   The client sends a message to a request queue and waits for a response on a callback queue.

2. Step 2: Eliminate other options

   Options A, B, and D describe direct function calls, HTTP calls, or streaming, which are not RabbitMQ RPC patterns.

3. Final Answer:

   Send message to queue, wait for reply on callback queue -> Option C

4. Quick Check:

   RPC client sends request and waits on callback queue [OK]

Hint: RPC client uses request and callback queues [OK]

Common Mistakes:

• Confusing HTTP requests with RabbitMQ messaging
• Thinking RPC skips waiting for reply
• Mixing streaming with RPC calls

3. Given this RabbitMQ RPC client code snippet, what will be the output if the server replies with '42'?

client.send_request('compute', payload)
response = client.wait_for_response()
print(response)

medium

A. 42

B. None

C. Error: No response received

D. compute

Solution

1. Step 1: Analyze client request and response

   The client sends a request with 'compute' and waits for the server's reply.

2. Step 2: Understand server reply effect

   The server replies with '42', so the client receives '42' as the response and prints it.

3. Final Answer:

   42 -> Option A

4. Quick Check:

   Server reply '42' is printed by client [OK]

Hint: Output matches server reply message [OK]

Common Mistakes:

• Assuming no response means error
• Confusing request content with response
• Expecting function name printed

4. You wrote a RabbitMQ RPC client but it never receives a response. What is a likely cause?

medium

A. The server is sending HTTP responses instead of messages.

B. The client did not declare or listen on the callback queue.

C. The client is using direct API calls instead of RPC.

D. The client sent the request to the wrong HTTP endpoint.

Solution

1. Step 1: Check client callback queue setup

   In RabbitMQ RPC, the client must declare and listen on a callback queue to receive replies.

2. Step 2: Identify why no response arrives

   If the callback queue is missing or not listened to, the client won't get the server's reply message.

3. Final Answer:

   The client did not declare or listen on the callback queue. -> Option B

4. Quick Check:

   Missing callback queue causes no response [OK]

Hint: Always declare and listen on callback queue [OK]

Common Mistakes:

• Confusing HTTP endpoints with RabbitMQ queues
• Ignoring callback queue setup
• Mixing direct API calls with RPC messaging

5. You want to build a service that processes tasks reliably even if the worker is busy or down. Which approach is best?

hard

A. Use direct API calls with HTTP for immediate responses.

B. Use local function calls without messaging or HTTP.

C. Use WebSocket connections for real-time task processing.

D. Use RabbitMQ RPC to queue tasks and get replies asynchronously.

Solution

1. Step 1: Understand reliability needs

   Reliable task processing requires queuing tasks so they are not lost if workers are busy or down.

2. Step 2: Match approach to reliability

   RabbitMQ RPC uses message queues that store tasks until workers process them, supporting asynchronous replies and retries.

3. Step 3: Compare other options

   Direct API calls and WebSockets require immediate availability and do not queue tasks reliably; local calls lack distribution.

4. Final Answer:

   Use RabbitMQ RPC to queue tasks and get replies asynchronously. -> Option D

5. Quick Check:

   Reliable async processing = RabbitMQ RPC [OK]

Hint: Queue tasks with RPC for reliability, not direct API [OK]

Common Mistakes:

• Choosing direct API for reliable queuing
• Confusing WebSocket with message queue reliability
• Ignoring asynchronous processing benefits