Christian Kerl

The enterprise platform was newly developed and the in-house sub-project deals with communication between the individual components. Data is read from various other third-party systems or received via various interfaces and forwarded to the target systems.

It is a pure backend system that works in a JBoss EAP together with Camunda BPM for process control.

One of the main problems is performance with the sometimes very extensive amounts of data, especially in conjunction with Camunda BPM.

An in-house developed application is mainly used for selling insurance; it must be constantly adapted to new products and legal regulations. It is used by internal employees as well as independent brokers.

The application is classically divided into frontend (client) and backend (server). The user interfaces are implemented within the Eclipse RCP framework, and there are also other "channels" with independent interfaces that only call the backend part via web services.

The internal structure is highly distributed across various subsystems and host implementations, so the entire analysis and development was accompanied by extensive coordination efforts.

A new web platform is being built for customer consulting, which helps to better present the advantages and disadvantages of current financial security. Internally, the platform is used directly by consultants and enables a uniform consulting process, largely designed according to their requirements. Customers also gain direct access to the platforms through various public access points and can assess their current situation independently.

The application is classically separated into frontend (client) and backend (server); the interfaces are implemented in a modern single-page variant with Javascript, and the backend is developed stateless with simple servlet containers. Communication between frontend and backend is enabled via various REST services and utilizes the advantages of Spring Boot. Other third-party systems are partially connected via legacy SOAP web services.

The internal structure of the application is distributed across further third-party services and is completely stateless. Even the storage of customer data takes place in a third-party system, making proprietary database systems obsolete. This allows the various individual applications to be developed with a high focus on functionality and reduced internal dependencies. This enables increased reusability of proprietary application building blocks.