Certified MuleSoft Platform Integration Architect

By Salesforce · Question Mode

QuestionQ8

VerifiedDesigning and developing Mule applications

An organization has developed a large monolithic application over many years and now wants to move to a microservices architecture. During this transition, it has created several System APIs as Mule applications that expose different functionality from the monolithic application. The System APIs are deployed to Mule runtimes on a customer-hosted AWS EC2 instance.

The System APIs connect directly to a single database used by the monolithic application. At present, every project must include a Database connector and its connector configuration. The organization plans to split this database into several smaller data stores in the future.

What MuleSoft-recommended best practice should be used to share the connector and configuration details across the APIs?

Explanation

A Mule domain centralizes shared global resources, including connector configurations, for Mule applications deployed to the same customer-hosted runtime. Placing the Database connector and its configuration in one domain lets every associated System API reference the same configuration, avoiding duplicated settings and credentials. Shared Resources (Mule Domains)

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!