TransRisk transformation - building a scalable and secure microservices architecture.

About the project

Client:

Trans.eu – a leading provider of IT solutions for the transportation industry, offering a platform for managing transport orders. One of the platform’s key features is the TransRisk index – a system that assesses the financial reliability of contractors based on historical data. Its main goal is to reduce the risk of working with unreliable business partners.

Project goal:

To migrate the system to a modern microservices architecture and develop version 2.0 of the TransRisk index, built on more efficient technologies. The project aimed to ensure greater flexibility, scalability, and security of the system, while also improving the indicator calculation process.

Customer experience

The large number of variables and the desire for continuous algorithm improvement pose a huge challenge. That’s why I really value the collaboration with fireup.pro in terms of ongoing solution development.

Grzegorz Szydłak

Product Owner

From challenge

Key Challenges

Migration to microservices

The transition to a microservices began with version 1.0 of TransRisk. For version 2.0, the main motivation was the lack of support for Elasticsearch 2.0, which posed security risks and led to increased infrastructure costs.

Migration of data sources:

As the client’s platform evolved, the need arose to incorporate new data sources delivered by microservices

Optimization of the TransRisk index

Enhancing the accuracy of calculations and the performance of the index, which helps users assess the credibility of business partners.

Verification of results

The transition to a new architecture required comparing the results generated by version 1.0 and 2.0, which was a significant challenge for the team.

Key functional and non-functional requirements:

Calculating the index based on an algorithm provided by the client, taking into account contractors' activity on the exchange and their financial history.

Ensuring a daily calculation schedule with proper error handling.

System scalability and flexibility to support a growing number of users.

Through the solution

Implementation process

The project was carried out iteratively using the Scrum methodology. Key stages included:

Familiarizing with the client's algorithm and refining it.
Migrating data from the old system to the new one.
Creating and verifying automated tests, followed by final validation of the results.
Gradual deployment of the new system with parallel comparative analysis between versions 1.0 and 2.0.

Innovations and technologies

Implementation of batch processing and integration with Kafka, enabling more efficient data stream management.
Transition from Elasticsearch to PostgreSQL, which improved system performance and security.
Use of the modern Quarkus framework, specifically designed for microservices and containerization.

To the success

Technological outcomes

Reduced indicator processing time

Managed to reduce the processing time from 3 hours in version 1.0 to just 1 hour in version 2.0.

Lower infrastructure costs

Achieved through more efficient microservice implementation technologies and the switch to a new database.

Improved scalability

Improvement enabling the platform to support a growing number of users.

Enhanced security

High standards achieved by eliminating risks associated with the unsupported Elasticsearch 2.0.

Performance boost

Performance enhancement resulting from the new architecture.

Business benefits

Streamlined process for assessing the credibility of contractors.

Reduced risk associated with unreliable business partners.

The TransRisk 2.0 project confirmed the value of long-term collaboration with the client, allowing the team to gain a deep understanding of their needs.