This is the first of a three part series on the Salesforce Developers codeLive channel where we walk through a lift and shift of functionality from Salesfore Apex to MuleSoft Anypoint Platform.
- Part #2 - Building the API implemtation
- Part #3 - Refactoring Apex & Building Flows
See this repo for all of the code and assets used in the applications.
The scenario for the demo is that your Salesforce org has an existing application to search for Delta and United flights. It consists of a simple Lighting Web Component, a controller and a service class that makes callouts to a Delta SOAP service and a United REST service.
Your new boss loves the service but wants you to make a number of enhancements:
- It needs to be easily discoverable by IT and other developers within your organization.
- She wants to use the service on the company website and by mobile applications so it needs to be easily accessible, consumable and reusable by IT and other developers.
- Since it will be used by other applications you’ll need to implement centralized governance and compliance.
- You’ll need to implement SLAs with monitoring, security and scalability.
- It will need to be extensible for future enhancements, including a current request to add a PostgreSQL DB for American Airlines.
To meet these requirements, your approach is to create an API on MuleSoft Anypoint Platform and move the callouts from the Apex class and this API implementation.
In the first day’s video we:
- Examine the existing Salesforce code
- Define the API with RAML, the Restful API Modeling Language
- Mock the API to test its design before building
- Make the API discoverable by adding it to the private Anypoint Exchange
