Summary
In this chapter, we have covered platform events in detail and discussed a number of ways in which we can both publish and consume them. We began the chapter by discussing what is meant by the term event-driven architecture and described how an event bus allows us to both publish and consume events and has an operating model that can be thought of as being analogous to how Twitter operates.
The next section then discussed the key use cases for platform events and how we can use platform events to decouple applications to make them easier to scale and grow. We also discussed how we can connect to external systems in a simpler fashion through the use of platform events.
With our understanding of these use cases in place, we then moved on to how we define a platform event and how a platform event is defined as metadata within Salesforce. We then looked at a number of ways of publishing events through the use of Apex, Process Builder, flows, and the Salesforce REST API....
