From the course: Microservices: Design Patterns
Join today to access over 24,500 courses taught by industry experts.
Asynchronous eventing
From the course: Microservices: Design Patterns
Asynchronous eventing
- The final data access pattern we will discuss is asynchronous eventing. While it needs to be talked about as a pattern, it is much bigger than this course. Check out my course in the library, Microservices: Asynchronous Messaging, to dive much deeper into this topic. Many times in a microservices architecture, you run into situations with long-running transactions or complex workflows that just cannot fit into a single blocking API call. Enter into the picture asynchronous eventing. The problems we can solve go beyond what I just described, but essentially in a nutshell, we can describe the superset of problems as some process that cannot be done in real time through a blocking call. The pattern deployed depends upon the use cases, but they all share a common thread, a service API that triggers the event. The event can cascade asynchronously from the API itself, putting together a series of actions that all happen behind the scenes after the client has received an accepted message…
Download courses and learn on the go
Watch courses on your mobile device without an internet connection. Download courses using your iOS or Android LinkedIn Learning app.
