In this video, explore common use cases for event-driven microservices using asynchronous messaging.
- [Instructor] One of the most common use cases … for asynchronous messaging in a microservices-based system … Oftentimes you will hear … of event-driven microservices being applied … to a data pattern and we will discuss that … when we talk about data. … But for the purposes of this chapter, … we are talking very generic about event-driven microservices … and how to apply them to your use cases. … An event-driven microservices pattern requires one … or more steps based on the invocation from a specific event. … These can be as simple as writing a tuple to a database … that are required when a specific system event occurs. … Again, the sky is the limit here … when working in these models, … but the key is one or more steps. … Those steps, however, are triggered from a single event. … We don't usually build event-driven microservices based … on several events being fired before kicking … off the workflow. … It is usually one single event. … Now, I won't say that there aren't cases … where there are a series of events needed, …
- 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