Salesforce Platform Events

Author

Platform Events are just like another custom object that is used to connect External sources through Business Processes in Salesforce.
Consider a scenario where an app in salesforce notifies to an external app and in another one where an external product app notifies Salesforce for completion of manufacturing. So here salesforce and external system communicate through Platform event messages.
Platform Events are part of the salesforce enterprising messaging platform and this platform provides an Event-driven architecture that enables the app to communicate inside and outside of Salesforce.

Event-Driven Software Architecture

An event-driven (or message-driven) software architecture comprises of:

  1. Event Producers
  2. Event Consumers
  3. Channels

In a large distributed system this architecture is suitable because it decouples event producers from consumers and therefore it simplifies the communication model in a connected system.

Some Important Components of Event-Driven Systems

Event: Event is defined as a change in state.
Event message: Event message is also known as event Notification. It contains data about the event.
Event Producer: It is a publisher of Event Message.
Event Consumer: It is defined as who receives messages or notifications from the event bus.
Channel: It is also known as Event bus in Salesforce through which an event producer sends a Message and consumer Subscriber to the channel to receive messages or notifications.

Goals of Salesforce Platform Events

The goal is to extend the existing capabilities of Integration options such as Outbound messages, Streaming API, Apex Callouts.

Use of Salesforce Platform Events in External Apps 

Platform Events enable the flow of event messages within Salesforce and or from External apps. Apps on salesforce can use Apex method, Apex trigger, or the empApi Lightning component to consume events. Declarative tools, such as Process Builder or Flow.

Events can be published in External apps using the SObject API and consumed by using CometD. There is a lot of flexibility to choose accordingly to use Platform Events!

Pranshu Goyal, Director of Products at Mirekta, states: “We envision DSM to be used by every small to a medium-sized organization dealing with bad data and want to get rid of duplicates easily with no cost. We have faced issues dealing with duplicates in our organization. That inspired us to make a solution that is not only simple to use but can be used widely to make the organization’s data clean to make them more efficient and productive. We want DSM to be a solution for every organization looking for duplicate management capability better than the Salesforce out-of-the-box solution with no additional cost.”

Recent Posts

Categories

Featured by