Transparency, openness and connectivity – the foundation of all we do
fintus Suite was developed under the condition that no monolith emerges. The result is a future-proof standard software based on modern technologies such as Docker, and proven frameworks such as SpringBoot, Angular or ElasticSearch. Since day one, development has been carried out using agile methodology.
We used the best of Scrum and Kanban for our software according to the situational requirements. We view its open system architecture as the key to integration and connectivity into any environment. We prefer REST APIs for communication between front and backend as well as third party components, while maintaining central graphically orchestrated process control.
fintus Suite was developed under the condition that no monolith emerges. The result is a future-proof standard software based on modern technologies such as Docker, and proven frameworks such as SpringBoot, Angular or ElasticSearch. Since day one, development has been carried out using agile methodology.
We used the best of Scrum and Kanban for our software according to the situational requirements. We view its open system architecture as the key to integration and connectivity into any environment. We prefer REST APIs for communication between front and backend as well as third party components, while maintaining central graphically orchestrated process control.
Technology stack
Up-to-date concepts for user-friendly utilisation
fintus Suite relies on state-of-the-art technologies and architectural concepts. The User Frontend (formerly known as COCKPIT) is user-friendly and requires no prior installation or plug-ins. The central process modelling is web-based and takes place via BPMN 2.0 standard, which ensures the central orchestration of the process landscape as well as the ability to react to internal and external events. Java, as an object-oriented and feature-rich programming language, forms the basis for the essential components of the executing layer. The data is stored in relational databases, with Microsoft SQL Server and the open source PostgreSQL solution being preferred. The flexible and low-maintenance operation takes place in Docker containers or classic Windows and Linux environments.
BPMN ENGINE
The graphic modelling of executable processes
Scenario 1, fintus Suite internal actions
The user or the system can trigger events from the suite’s various components. These events initiate one or more associated BPMN processes. These contain modelled logic, which includes various data sources, such as web services and local databases, as well as the ability to interact with third-party applications.
Scenario 2, fintus Suite external actions
Third party systems can communicate either via standard backend APIs or directly with fintus Suite’s BPMN engine. Suite interactions related to data exchange, the creation or modification of activities, or the enrichment of a business case are common scenarios. The standard APIs are available via OpenAPI/Swagger.
System requirements
Hardware and software requirements for the operation of the fintus Suite on your own premises: Windows Server from 2012 R2, alternatively Debian Linux. Java Runtime Environment from 1.8.0. Internet Explorer from version 11 (earlier versions on request). Microsoft SQL server from 2012 or PostgreSQL from 9.3, Windows-/Samba-FileServer.
Hardware requirements for 50 concurrent users: 4 (virtualised) CPU-cores, 24–32 GB RAM, SSD storage or similar. The operational monitoring implemented is based on Icinga monitoring components supplied by us.