Event/message bus integration
All the integration methods we have discussed so far rely upon the request/response life cycle that is at the core of how the internet and client-server systems interact using the HTTP protocol.
Conversely, event bus integrations utilize a pub/sub model whereby an event (or message) is published to a specific channel on the event bus. Different systems or processes can then choose to become a subscriber to events on this channel. The subscribers all then receive the event and choose how to react to its payload. This is shown at a high level in the following diagram:
Figure 12.1 – Events published to an event bus and consumed by subscribers
Salesforce provides an event bus on which standard messages (such as those from the Change Data Capture product) are sent, and onto which developers and administrators can publish their own custom events through the Platform Events system (which we will cover in detail in Chapter...
