Book Image

MuleSoft for Salesforce Developers

By : Arul Christhuraj Alphonse, Alexandra Martinez, Akshata Sawant
Book Image

MuleSoft for Salesforce Developers

By: Arul Christhuraj Alphonse, Alexandra Martinez, Akshata Sawant

Overview of this book

MuleSoft for Salesforce Developers will help you build state-of-the-art enterprise solutions with flexible and scalable integration capabilities using MuleSoft’s Anypoint Platform and Anypoint Studio. If you’re a Salesforce developer looking to get started with this useful tool, look no further. This book will get you up to speed in no time, leveling up your integration developer skills. This essential guide will first introduce you to the fundamentals of MuleSoft and API-led connectivity, before walking you through the API life cycle and the Anypoint Studio IDE. Once you have the IDE set up, you’ll be ready to create Mule applications. You’ll look at the core components of MuleSoft and Anypoint Platform, and before long you’ll know how to build, transform, secure, test, and deploy applications using the wide range of components available to you. Finally, you’ll learn about using connectors to integrate MuleSoft with Salesforce and to fulfill a number of use cases, which will be covered in depth, along with interview and certification tips. By the end of this book, you will be confident building MuleSoft integrations at an enterprise scale and be able to gain the fundamental MuleSoft certification – MCD.
Table of Contents (21 chapters)
1
Part 1:Getting Started with MuleSoft
7
Part 2: A Deep Dive into MuleSoft
14
Part 3: Integration with Salesforce and Other Connectors

Getting started with OAS and RAML

Open API Specification (OAS) and RAML are the two most extensively used API description formats. Anypoint Designer lets you create a REST API using RAML or OAS (previously known as Swagger).

Although they both have a lot in common, it’s essential to understand the capabilities of both OAS and RAML so that we can choose our API specification language wisely.

OAS

OAS is an open source specification language founded in 2010 with huge community support. Its fundamental purpose is to keep API documentation, libraries, and code in sync:

  • It supports both JSON and YAML to design API
  • OAS is ideal if your application has response type-only JSON, as it takes a longer time to load other formats
  • It is not very feasible in terms of code fragmentation and reusability
  • It focuses more on the documentation of an API

Let’s move on to RAML.

RAML

RAML was founded by MuleSoft in 2013 with the goal of providing all...