Difference Between Platform Events and REST API

 Platform Events:

  • Event-Driven Architecture:
    Platform events are designed for a pub/sub model, where publishers send messages (events) and subscribers receive them. This allows for loosely coupled integrations, where systems don't need to know about each other's internal workings.
  • Real-time Notifications:
    They are used to notify subscribers about specific events happening in Salesforce, such as record changes or custom events.
  • Asynchronous:
    Platform events are processed asynchronously, meaning the publisher doesn't wait for a response from the subscriber. This can improve performance and scalability.
  • Examples:
    Publishing a platform event when a high-value opportunity is created, or when a customer's address changes.
  • Pub/Sub Model:
    They follow a publish-subscribe model. A publisher sends an event, and any number of subscribers can listen for and react to that event. 
  • Scalability:
    Platform events are designed to handle a high volume of messages, making them suitable for large-scale integrations. 
  • Examples of use cases:
    Real-time monitoring, custom notifications, and triggering actions in external systems. 
REST APIs:
  • Request-Response Model:
    REST APIs are based on a request-response model, where a client sends a request to a server, and the server sends back a response. 
  • Synchronous:
    REST API calls are typically synchronous, meaning the client waits for the server to process the request and send back a response.
  • Data Operations:
    They are used for performing CRUD (Create, Read, Update, Delete) operations on Salesforce data, as well as retrieving data. 
  • Examples:
    Retrieving account information, updating a contact record, or creating a new case.
  • Flexibility:
    REST APIs offer more flexibility in terms of the data that can be sent and received, making them suitable for complex data interactions. 
  • Examples of use cases:
    Integrating with external systems, building custom user interfaces, and automating data processes. 
Key Differences Summarized:
Feature
Platform Events
REST APIs
Architecture
Event-driven (pub/sub)
Request-response
Communication
Asynchronous
Synchronous
Purpose
Notifications, real-time updates
Data manipulation, retrieval
Complexity
Simpler for notifications
More complex for data operations
Scalability
High volume, scalable
Can be less scalable with high volume
Use Cases
Real-time monitoring, custom notifications, triggering actions in external systems
Integrating with external systems, building custom user interfaces, automating data processes

Comments

Post a Comment

Popular posts from this blog

My Trigger Scenario's

 Scenario 1 : Prevent Contact Update by Same User Within 1 Hour ? Trigger TimeLastmodified on Contact (Before update) {     Set<Id> contactIds = new Set<Id>();     for (Contact con : Trigger.new) {         contactIds.add(con.Id);     }     for (Contact newCon : Trigger.new) {         if (newCon.LastModifiedById == UserInfo.getUserId()) {             Long minutesSinceLastUpdate = DateTime.now().getTime() - newCon.LastModifiedDate.getTime();             minutesSinceLastUpdate = minutesSinceLastUpdate / (60 * 1000); ...
Read more

Configure types Of Products in CPQ and Revenue Cloud ?

Image
 1) Non-Subscription/One-Time Product : In CPQ :  1)As the name suggests such products are sold as one-time purchases or do not involve recurring billing        or subscription-based pricing.  2) These products are typically purchased once and do not require ongoing payments or renewals.                                          In Revenue Cloud :  2) Subscription Product :   Subscription products are sold as services that last for a specific period (whether that's days, months, or years). Subscription products have recurring payments associated with them. Upon contracting these products become a Subscription  associated with the Contract and renewals can be generated. Example:  Netflix or Amazon Prime. Or buying a cell phone subscription for a month.   In CPQ : Required Fields a...
Read more

Steps for Calculate Derived Pricing in RCA ?

Image
 Step 1) Create Normal Product and Price Book Step 2) Create  One More Product with Pricing to make Is Derived = True Step 3) Now Create Derived Pricing Record Like Below. Step 4) Open " Discovery Procedures " Object and Open existing " Default Discovery Procedure "                         Record.             Update existing " Context Definition " as " SalesTransactionContextMK ". Step 5) Open " Default Discovery Procedure V1 " Procedure.   Update "Asset Discovery" Node and Save and Activate. Step 6) Go Decision Table's and Refresh "Price Book Entries V2" and "Derived Pricing Entries"   Then test add the Product's Quote Line Here is the expected output In "Derived Price" Object While creating the Record, If Pricing Source is "Header"                          Expected Output
Read more