According to MuleSoft a synchronous invocation of a RESTful API using HTTP to gel an...

In system integration, different interaction patterns are used depending on the communication requirements between systems. For a synchronous invocation of a RESTful API using HTTP to get an individual customer record from a single system, the Request-Reply pattern is used. Here’s a detailed explanation:

Request-Reply Pattern:

Definition: This pattern involves a client sending a request to a server and waiting for a reply. The communication is synchronous, meaning the client waits for the server to process the request and send back the response.

Typical Use Case: It is used when immediate feedback is required from the server, such as retrieving a specific customer record.

RESTful API and HTTP:

Synchronous Communication: HTTP is inherently synchronous, making it suitable for Request-Reply interactions where the client expects an immediate response.

Data Retrieval: Commonly used for GET requests in RESTful APIs to retrieve data from a server.

Example:

Scenario: A client application requests customer details by making a GET request to a RESTful API endpoint. The server processes the request and returns the customer record.

References

MuleSoft Documentation: Integration Patterns

REST API Design: Request-Reply Pattern