Asynchronous Communication: Difference between revisions
Jump to navigation
Jump to search
| Line 5: | Line 5: | ||
=Overview= | =Overview= | ||
Asynchronous communication is a communication model used by [[Distributed Systems|distributed systems]] where a sender produces data, also referred to as message, and hands it over to delivery to an intermediate system, not expecting an immediate response to it. The message can reach zero, one or more receivers. Asynchronous communication is fundamentally different from its [[Microservices#Synchronous_Communication|synchronous counterpart]] in that the application thread that sends the message does not block waiting for an answer, but it can move onto performing additional processing. | Asynchronous communication is a communication model used by [[Distributed Systems|distributed systems]] where a sender produces data, also referred to as message, and hands it over to delivery to an intermediate system, not expecting an immediate response to it. The message can reach zero, one or more receivers. Asynchronous communication is fundamentally different from its [[Microservices#Synchronous_Communication|synchronous counterpart]] in that the application thread that sends the message does not block waiting for an answer, but it can move onto performing additional processing. | ||
A response may not be expected at all, and when it is expected, additional logic must be deployed to receive and handle it. | |||
=Systems= | =Systems= | ||
* <span id='Kafka'></span>[[Kafka]] | * <span id='Kafka'></span>[[Kafka]] | ||
Revision as of 17:02, 5 October 2023
Internal
Overview
Asynchronous communication is a communication model used by distributed systems where a sender produces data, also referred to as message, and hands it over to delivery to an intermediate system, not expecting an immediate response to it. The message can reach zero, one or more receivers. Asynchronous communication is fundamentally different from its synchronous counterpart in that the application thread that sends the message does not block waiting for an answer, but it can move onto performing additional processing.
A response may not be expected at all, and when it is expected, additional logic must be deployed to receive and handle it.