why does adesso use MuleSoft?

[suchona.kani.z]

We often come across solutions in which customers rely on point-to-point integrations and implement their own backend service connections for each client (mobile/web, etc.). In the best case, microservices are used here too and connected to the respective components. But this also has its limits. They are usually on time, inexpensive and often sufficient for a single client. Nevertheless, these solutions are very often only partially reusable, firmly linked to their components and difficult to expand when changes occur.

To do this better, we follow the APILed approach proposed by MuleSoft. The services are divided into a three-layer system: Experience, Process and System Layer.


The three-tier system, source: MuleSoft

The clients access the APIs in the Experience Layer. Each client can claim its own Experience API. These provide the desired functionalities and access the APIs in the Process Layer. The business functionalities are implemented in the Process Layer. Since business logic usually requires data from external systems, they access the System Layer APIs. Only cayman islands consumer email list​ the API layer has a direct connection to the actual systems and communicates with them (for example databases, other SOAP/REST services, Salesforce and SAP). Each service is specialized in one system and only takes care of its connection. The APIs can be protected in all layers with a client ID/secret definition or an SSH key deposit.

Another essential fact as to why we use MuleSoft is the Java basis of the entire microcosm. Any Java developer will immediately notice that the development environment is a further development of Eclipse. The project structure with sources and resources folders is reminiscent of a normal Java application at first glance. By embedding Maven, we can access a large repository world. Of course, MuleSoft also provides one or two standard repos.

Common/System Properties and Spring Enterprise Beans make the API suitable for any environment. The integration of the Java Keystore/TrustStore process also makes the complicated encryption/decryption principle familiar and easier to handle. Due to the already existing in-depth Java expertise, the transition was particularly easy.