Breaking News: Grepper is joining You.com. Read the official announcement!

Problem: Long Running Operations Can't Handle with Sync Communication

Add Answer

Anjali Sharma answered on February 2, 2023 Popularity 2/10 Helpfulness 1/10

answer Problem: Long Running Operations Can't Handle with Sync Communication

Problem: Long Running Operations Can't Handle with Sync Communication

Comment

Problems

● HTTP calls to multiple microservices

● Chain Queries

● Visit more than a few microservices

● Increased latency with Highly Coupling Services

● Performance, scalability, and availability problems

Best Practices

● Minimize the communication between the internal

microservices

● make microservices communication in

Asynchronous way as soon as possible.

Solutions

● Asynchronous Message-Based Communications

● Working with events

HashMap<String, Long> params = new HashMap<>();
params.put("userId", orderDetails.getUserId());
try {
    ResponseEntity<User> response
        = new RestTemplate().getForEntity(
            "http://localhost:8080/users/{userId}",
            User.class, params);
}
catch (Exception ex) {
    throw new InvalidUserIdException(
        "User Id " + orderDetails.getUserId()
        + " Not Found");
}

https://learn.microsoft.com/en-us/azure/architecture/patterns/async-request-reply

Popularity 2/10 Helpfulness 1/10 Language javascript

Source: Grepper

Tags: communication handle javascript operations sync

Link to this answer
Share Copy Link

Contributed on Feb 02 2023

Anjali Sharma

0 Answers Avg Quality 2/10

Problem: Long Running Operations Can't Handle with Sync Communication

Contents

More Related Answers

Problem: Long Running Operations Can't Handle with Sync Communication

Grepper

Documentation

Social

Legal

Contact

Oops, You will need to install Grepper and log-in to perform this action.