My Study Notes for Salesforce Certified Mulesoft Developer - Level2. Go thru chapter wise (DataSheet) reference links for each topic provided below and make notes for quick reference. Take Mulesoft Certified Developer Level2 Practice test provided by MuleSoft training as many times as possible @ https://training.mulesoft.com/certification/developer-mule4-level2/practice-exam MCD Level2 - DataSheet Ch1:Expose production-ready Anypoint Platform managed APIs from Mule applications https://help.mulesoft.com/s/question/0D52T00004mXYC6SAO/horizontal-scaling-vs-vertical-scaling-of-mule-workers Implement versioning of specific API-related artifacts https://docs.mulesoft.com/exchange/to-change-raml-version https://forum.raml.org/t/as-versions-is-managed-in-raml/788/3 Configure custom or out-of-the-box (OOTB) API policies https://docs.mulesoft.com/gateway/policies-included-http-caching https://docs.mulesoft.com/api-manager/1.x/json...
The Salesforce Composite API and Composite Graph API are both REST API resources designed to execute multiple operations in a single API call, reducing the number of round-trips and optimizing API usage. However, they differ significantly in their capabilities, limits, and use cases. Salesforce Composite Request The Composite API allows you to execute a series of REST API subrequests in a single call, with the output of one subrequest potentially used as input for subsequent subrequests. It’s designed for simpler, sequential operations. Key Features Endpoint : POST /services/data/vXX.X/composite Subrequest Limit : Up to 25 subrequests in a single call. Supported Operations : Supports CRUD operations (Create, Read, Update, Delete), SOQL queries, and other REST API resources (e.g., sObject operations, query, queryAll). Execution : Subrequests are executed sequentially in the order specified in the request body. Dependency : Subrequests can reference the output of previous...
In MuleSoft CloudHub 1.0, persistent queues and batch job queues are mechanisms to ensure reliable message processing and handle large datasets asynchronously. They are stored and managed differently but work together to provide scalability and reliability . Persistent Queues : Persistent queues in CloudHub 1.0 are used for reliable message delivery across Mule applications, particularly for VM (Virtual Machine) connectors or when distributing workloads across multiple workers. They are backed by CloudHub’s Cloud Queue Storage (CQS) , which uses Amazon SQS under the hood for persistence. When enabled in the Anypoint Runtime Manager (via the "Persistent Queues" checkbox) , all VM queues in the application are stored persistently in CQS, overriding any transient queue settings in the Mule configuration. Data in persistent queues is stored in the same region as the worker (e.g., AWS SQS in the deployed region) and survives worker restarts or crashes, ensuring zero mes...
Comments
Post a Comment