Microservices architecture
Optimized deployment process
Multi-OS support
Rich data available in logs
A US insurance leader approached us with an ambitious project implying a complete application revamp and new features development. The business application provides functionality for real estate title insurance and reinsurance, which both client’s agents and partners use in their day-to-day work.
Before Symfa joined the project the system had been under continuous development for 6 years and by that time it had grown significantly. But along with the growth, the app had become hard to maintain due to countless dependencies in the monolithic architecture. Another problem was that both frontend and backend components were running on unsupportable software versions, which was a source of potential security breaches. These issues impeded new functionality development the client needed to cover their evolving business requirements. To breathe new life into the system, the customer initiated a comprehensive application migration endeavor along with new features development.
The legacy system was represented by a huge monolith application that had to be splitted into microservices and migrated to the cloud correctly and without losses. Taking note of the project size and complexity, the migration process was to be slow-paced and as meticulous as possible. Simultaneously, recognizing the client's urgency for additional features, we initiated the development of new functionality promptly, without waiting for the completion of the entire migration process.
We conduct comprehensive application migration, which includes cloud migration, .NET to .NET Core, and microservices migration. In addition, the team implemented the cross-function feature to eliminate dependency on Windows OS.
Frontend and backend components, and static files were placed in separate repositories. This helped to reduce deployment time from 45 to 5 minutes and alleviate the overall system maintenance in the cloud.
To implement microservices architecture in the cloud environment, we leveraged Docker containers, Kubernetes and proceeded with configurations in Azure pipelines through Azure DevOps.
Instead of default Microsoft logging we implemented Splunk logging. This enabled the customer to gain more precise and rich data about requests and also apply filters (by period, endpoints, or environment).
For PDF-files generation, the monolith app utilized the Font library, which is unsupportable by .NET Core. We replaced it with a new library and updated the feature.
At the moment we continue supporting the legacy monolith application to ensure smooth day-to-day operations of the client’s staff. Approximately 70-80% of the functionality has already undergone migration, and the team consistently receives requests from the client for the delivery of new features.
We also initiated greater team involvement in the client’s business and metrics management, and the initiative was encouraged by the customer.
Comprehensive system migration allowed us to accelerate the release time significantly and also alleviate the maintenance of the ever-growing system. The updated functionality aids the customer in streamlining the insurance processes and enhancing the efficiency of the field staff.
Our team will get back to you promptly to discuss the next steps