Processing...
Δ
Insurance
Web Development, SaaS
Kotlin, Scala, Java
The client has several solutions designed to provide mandatory insurance coverage for U.S. citizens. One product is benefit software for insurance carriers and brokers that empowers all end-users with an automated, insight-based experience and simplified administration. Because there is separate legislation in the U.S., the company serves both public and private insurance organizations.
Initially, NIX engaged with the client’s in-house team to deliver new extended functionality for the existing monolith, legacy, multi-tenant platform that helped to reduce time spent on connecting each new tenant and provide end-users with more customization options. Impressed by our technical know-how in developing large-scale enterprise platforms, the client extended our collaboration to build a new microservice-based SaaS platform from the ground up that will deliver services for a huge customer base quickly and efficiently.
Build an architecture for a new SaaS solution that will provide enough high-load capacity to support more than 50,000 end-users simultaneously on an everyday basis.
Transfer all data and business logic from a monolith Java-based legacy platform to a new microservice platform
The original legacy platform version was too resource-intensive with unfavorable tenant process time-to-market—more than six months—which drastically affected customer satisfaction. The platform was too hard to manage efficiently and provide enough customization options.
As a part of the reinforcement of the legacy system, the our team:
The process of connecting new tenants required the creation of a new independent codebase on the client’s side. If another client made the same customization request, it was impossible to reuse the code, thereby reducing time spent on configurations.
This is why the NIX team implemented a new approach that has one shared part and the other one configurable. Our business analysis team determined the level of importance for each customization option that must be made on the configuration side. NIX engineers set up the process from scratch—namely how to maintain, store, and test the code using the new approach—and composed a step-by-step code review tutorial for everyone, which reduced code inconsistencies and helped the whole development team.
But all enhancements didn’t provide enough flexibility and scalability for the efficient management of tenants. The client’s aim was to significantly simplify all processes related to the new tenant connection without spending too much time and resources.
So the NIX team shifted to the next project phase—creating a new SaaS system from scratch for new tenants, leaving an enhanced legacy platform for the existing one.
Unlike the legacy system that required individual hardware, databases, and separate services for each new tenant, the new platform provides core functionality placed on the client-side and multiple configured services upon the tenant’s requests. There is no need to create a new service each time, and this significantly reduces tenant connection time and saves the client money.
The NIX team built a new microservice platform that supports multi-tenancy and allows adding any configuration on demand. The new SaaS platform is scalable enough to support a huge number of tenants and has a fast and efficient enrollment process.
Based on our extensive expertise, we created three QA automation training courses that are actively used by NIX and on the client-side. The training includes video materials, knowledge libraries—such as the description of DevOps process settings—and practical exercises, which are then checked by our QA automation experts. This education process helps all team members be on the same page and ensures the high quality of the QA procedures.
The client received an enhanced legacy platform that is now more flexible than ever in working with customization requests for existing tenants due to ingested microservices. The newly developed microservice-based SaaS platform has a perfectly scalable architecture to provide services for over 50,000 insurance tenants and allows end-users to enroll, manage, and share benefit information more efficiently.
As a result, NIX works with two platforms and provides continuous support for an entire base of active clients along with the following enhancements:
Reduced time-to-market
Initially, this process on the legacy platform required six months to develop and customize based on a specific request for each new tenant. Now it takes only a couple of months, which significantly reduces time to market and allows the introduction of more tenants in less time.
Cost-effectiveness
With the new system, we introduced a new role—experts who have both QA and development skills. With knowledge of HTML and CSS, they can customize UIs quickly and efficiently for each client without changing the platform backend. This role allowed us to decrease development expenses for the client since configurators are less resource-demanding than full-stack developers.
2 Project Managers, 3 Business Analysts, 7 QA Team Leads, 43 QA Engineers (34 Automation), 8 DevOps, 7 Java Team leads, 48 Java Developers, 3 .NET Developers, Configurators, GA/GTM
Kotlin, Python, Scala, MS SQL Server, Kubernetes, .NET Core, Selenium, Apache Groovy, Geb, Lombok, RxJava
Schedule Meeting
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.