function readOnly(count){ }
Sign Up ›
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
Learn More

Browse by Topic
ShowAll Questionssorted byDate Posted
+ Start a Discussion
PriyaKPriyaK 

which pattern does Metadata API follows ?

which pattern does Metadata API follow?
- Remote Process Invocation—Request and Reply or 
- Remote Process Invocation—Fire and Forget or 
- Batch Data Synchronization or
- Remote Call-In or
- UI Update Based on Data Changes
Raj BasakRaj Basak
Remote Call-In
PriyaKPriyaK
thanks for your reply Raj.
can you explain why it can not be Remote Process Invocation—Fire and Forget?
Raj BasakRaj Basak
If I considering generic architectural pattern then as Metadata API supports both read and modify (add/update/delete), so you can consider Add/update/delete using Metadata API as "Fire and Forget" pattern and it is being invoked by external system.

However in the context of SFDC patterns, "Remote Process Invocation—Fire and Forget" has a specific direction - SFDC to external application. That's why I didn't include "Remote Process Invocation—Fire and Forget" as SFDC is not initiating this interaction.