Given the diagram below, a Salesforce org, middleware, and Historical Data store exists with connectivity between them.
Historical records are archived from Salesforce and moved to a Historical Data store (which houses 20 million records and is growing) are fine tuned to be performant with search queries.
When reviewing occasional special cases, call center agents that use Salesforce have requested access to view the historical case items that relate to submitted cases.
Which mechanism and patterns are recommended to maximize declarative configuration?
- Use an ESB tool with Request and Reply pattern and then make a real-time Apex callout to the ESB endpoint to fetch and display historical data in a custom lightning component related to Case object.
- Use an ESB tool with a Fire and Forget pattern and then publish a platform event for the requested historical data.
- Use an extract, transform, load (ETL) tool with a Batch Data Synchronization pattern to migrate historical data into Salesforce and into a custom object (Historical Data) related to Case object.
- Use an ESB tool with Data Virtualization pattern, expose OData endpoint, and then use Salesforce Connect to consume and display the external object alongside with the Case object.
Reveal Solution Next Question