Micro Frontend is a somewhat new concept in frontend development based on the idea of splitting complex web applications into smaller, independent units. This enables attractive benefits such as easier scaling, faster development, improved maintainability and more flexibility. No wonder acrevis Bank's development team is interested in the micro frontend approach. But is the approach suitable for the bank's specific system landscape?

A partner was sought to implement a proof of concept for the micro frontend approach in combination with Camunda 7 based on the employee portal of acrevis.

In earlier discussions adesso was already able to position itself as a competent, flexible partner and was thus assigned with implementation of the proof of concept.

The most important requirement, and at the same time the biggest challenge, was that the individual micro frontends form independent components so that they can be reused flexibly in the future.

adesso factored this into the solution and built three micro frontends with associated micro services in the completed PoC for the acrevis staff portal. Internally, these communicate via REST API and WebSocket. The process logic was mapped with a single Camunda module and communication to this module runs via a message queue. The communication between the micro frontends, as well as the linking of the frontends into a single application, is complex. Here, the decisive advantage of the micro frontend approach is that a team-split implementation is possible. This means that fewer conflicts arise during development and the individual micro frontends can also be started and tested separately from one another.