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

Best practices and tips

We shall now learn some of the API best practices and tips. In order to get started, let’s learn some commonly used API design naming conventions.

API design naming convention

Although every organization may have its own set of guidelines and best practices for API design, here are a few commonly used naming conventions while designing an API. Adhering to the naming conventions throughout the API makes it look consistent and standardized:

  • Follow standard naming conventions for all the APIs. A commonly used format is <project_name><API-led-connectivity-layer>-api – for example, musicbox-sys-api.
  • Folder names should be in lower camel case – for example, dataTypes, examples, and musicboxAssets.
  • Filenames should be in lower snake case for readability purposes – for example, post-songs-datatypes.raml and get-songs-example.raml.
  • RAML declarations should be in lower camel case – for example...