What is the MuleSoft-recommended best practice to share the connector and configuration information among the APIs?
A.
Build a Mule domain project, add the Database connector and configuration to it, and reference this one domain project from each System API
B.
Build a separate Mule domain project for each API, and configure each of them to use a file on a shared file store to load the configuration information dynamically
C.
Build another System API that connects to the database, and refactor all the other APIs to make requests through the new System API to access the database
D.
Create an API proxy for each System API and share the Database connector configuration with all the API proxies via an automated policy
The MuleSoft-recommended best practice for sharing the connector and configuration information among multiple APIs is to use a Mule domain project. The steps are:
Create a Mule domain project.
Add the Database connector and its configuration to the domain project.
Reference this domain project from each System API that needs to use the Database connector and configuration.
By using a domain project, you centralize the configuration and reuse it across multiple APIs. This approach ensures consistency, reduces duplication, and simplifies maintenance and updates to the connector configuration.
References
MuleSoft Documentation on Domain Projects
Best Practices for Reusable Configuration in MuleSoft
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit