In this video, explore use cases around point-to-point asynchronous communications in microservices architectures.
- [Instructor] As previously mentioned, … point to point asynchronous messaging … is one of the most common uses of this communication style. … I want to take a look at when you would use it … and how it is constructed. … The use cases can be endless but they tend … to fall into a few groups of classifications. … The first and, probably, the most common … is when no response is needed. … If the client of the service doesn't really need … to know that the task is done, … there is no real valid reason to wait … for it to finish. … As such, you can produce a message … and fire it off and, essentially, … A place I've used this a lot is with audit records … that are not mission-critical. … If the audit record itself is not a hard and fast … system requirement, there is no reason … to wait for it to get written. … You can fire a message to the Message Broker … intended for the audit system and just expect it … to get written. … Now, of course, you can't guarantee that it is written, … or even done so in a timely manner in this model but, …
- Gains and tradeoffs of asynchronous communications
- Use cases for interservice communication patterns
- Event-driven microservices
- Use cases for choreographed and orchestrated events
- Streaming data platforms
- Data flows, migration, and synchronization