Publish-subscribe

- [Instructor] The publish-subscribe asynchronous messaging style is a little bit unique and its use cases are very much in the same boat. But when you need them, the power is evident. The use cases are very specific and much of them deal with real issues in distributed computing. The multiple responders use case is one such, especially in distributed computing. Oftentimes, we see cases when the flow of traffic between sites is limited on purpose to enforce good constraints across the data centers. We often allow data to stay in sync between sites, but what happens when you need more than data in sync? For instance, you may allow your databases to stay in sync across data centers, but other triggered actions are data center independent. In a pub/sub model, you can federate the message broker across multiple data centers and allow triggered actions within each data center to occur in isolation. Those triggered actions are…