Thanks Jitendra, this makes a lot of sense even for my current requirement.

One follow up question for this scenario. If the validation rules themselves are mastered in another system & the draft quote details are validated from a real-time call to another system (to check everchanging LATEST UPDATED validation rules), does it make sense to create same validation rules in Salesforce side also, so that if sync fails due to bad quote data, user can fix that data & wait for resync, or flag that quote & move on?

I am working on building integration framework document that helps to follow standard path to connect between systems. As we do have multiple integration patterns to connect systems, It would be tough to stick with single framework. Could you please share some ideas on building this.

How I read that limit:
If I used e.g. Mulesoft to subscribe to a Salesforce platform event / CDC then this 50k per day (24hours) would apply. But this 50k daily limit is also shared with CometD clients inside Salesforce e.g. EmpAPI component.

Streaming API docs mention that the limit of delivered PushTopics is actually 1M per day (24 hours).

Comparing 50k vs 1M seems a bit (I mean a lot) sad.

Another comparison – Outbound messages do not seem to have allocations and limits around delivered messages (on the other hand there is the issues with potentially not delivering the messages in order)

Almost as if the main use case was to use platform events / CDC for event driven architecture “inside” the Salesforce platform (potentially also allowing outside systems to publish on the event bus and subscribing inside Salesforce) but not to communicate outside?

Am I misunderstanding the limits? Apart from this I am a fan of Platform events 🙂

I am having multiple requirements and want to check feasibility of platform events.

1. On Opportunity close I need to update multiple external applications Currently I am using multiple Batch APEX approach and running the batch in every 10 mins. While performing this API callouts need to generate JSON request with multiple fields on opportunity and opportunity child objects. In some of the cases external systems are updating my opportunity as callback using SF data API/composite API. Can I use platform event as Fire and forget to notify external systems and the call back will remains same as is?

2. There are multiple future calls in opportunity process execution, Can I replace future calls with platform events?

3. The current daily volume of cases is very huge around 75 K opportunities per day and I am using Enterprise edition org. Will platform event suitable for such high volume of cases per day.

I am having multiple requirements and want to check feasibility of platform events.

1. On Opportunity close I need to update multiple external applications Currently I am using multiple Batch APEX approach and running the batch in every 10 mins. While performing this API callouts need to generate JSON request with multiple fields on opportunity and opportunity child objects. In some of the cases external systems are updating my opportunity as callback using SF data API/composite API. Can I use platform event as Fire and forget to notify external systems and the call back will remains same as is?

2. There are multiple future calls in opportunity process execution, Can I replace future calls with platform events?

3. The current daily volume of cases is very huge around 75 K opportunities per day and I am using Enterprise edition org. Will platform event suitable for such high volume of cases per day.