In this session we talk about how to Integrating with Salesforce using Platform Events.
Agenda :-
- Point to Point Integration Challenges
- Solution – Event Driven Architecture
- Understanding Platform Events
- Publishing & Subscribing to Platform Events
- Demo
- Q & A
Point to Point Integration Challenges
- Scalability Inclusion and removal of entities to the communication is time consuming
- Tight Coupling Dependency on every integration point makes it maintenance heavy
- Non Ubiquitous Communication Inconsistent & disparate data exchanges formats
The Solution – Event Driven Architecture
Anatomy of an Event Driven Architecture
Understanding Platform Events
- Sobject like Salesforce Entity
- Suffixed with __e
- ReplayID for replaying specific event
- Pub/Sub based communication
- No polling required
- Heterogeneous payloads
- Define events with different payloads
Here is recording for Session.
Here is PPT of Session.
Please Subscribe to the channel to get notification for upcoming recording.
If you are new in Salesforce. Please check our free Salesforce Admin and Salesforce Developer training.
Thanks,
Salesforce Apex Hours
2,940 total views, 6 views today
Amit Chaudhary is Salesforce Application Architect and working on Salesforce Platform since 2010. He is Salesforce MVP since 2017 and have 13 Salesforce Certificates.
He is a active blogger and founder of Apex Hours.
As platform event is similar to object and publish event has payload same as field api name and value like
{
“OrderNumber”:”101″,
“Status”:”Shipped”
}
But what if we want to send Order with Order Product where order product would be multiple payload would be
{ “OrderNumber”:”101″,
“Status”:”Shipped”
“OrderProduct”:[
{
“OrderProduct”:”P101″
}.
{
“OrderProduct”:”P102″
}
]
}
And what is limit of data that we can publish in case above scenario.