Why HTTP based Microservices is a BAD idea. | explained with example

When discussing monolithic apps, we stated that this type of communication takes place between processes.

In essence, synchronous communication is defined as using the HTTP or gRPC protocol to return sync responses. The customer submits a request and waits for the service to respond. Therefore, client code must block its thread until the server’s response arrives. That implies that the client calls the server and has its operations blocked.

Asynchronous communication basically involves the client sending a request but not waiting for a response from the service. The client shouldn’t have blocked a thread while waiting for a response, which is the main point in this situation.