MAPFRE
Mapfre self-service Cloud migration AWS
The project
MAPFRE has had a self-service solution for years, such as web and mobile applications that allow its customers to have a complete set of services offered through various channels, where it is possible to manage insurance and make queries from anywhere and at any time, through a simpler and more intuitive experience.
The solution implemented is based on a fundamental concept, and that is that all development has been carried out under the same common code base regardless of the channel for which the applications are generated. In other words, it is the same common code base for both the private user service web portal and the apps for iOS and Android, which offer the same functionalities.
The solution developed to date was adequate in many aspects, especially in the backend development and mediation of services, which made it necessary to completely rethink the project due to shared IT infrastructures, non-digital infrastructures, non-digital operation, little capacity for personalisation of the digital product, MAPFRE's digital client identity dispersed among systems or difficulty in technological innovation.
Challenges
-
Qualitative and quantitative improvement of portal performance through a global network. -
Reduction of access times in navigation -
Improving customer experience by avoiding overcharging. -
Provide mechanisms to avoid server collapse and availability in the event of internet outages (alternative routes).
The solution
Some of the achievements include the following:
- New organisational structure and team collaboration.
- New way of working following Agile methodology ("MAPFRE's Agile Red Book") which can also be extrapolated to other areas of the company.
- Cost audit of digital channels vs. SI24 as a benchmark.
- Increased speed of delivery, traceability of MVPs and data culture.
- Motivation of teams via OKR's by meeting annual targets and seeing the impact on their business areas.
In terms of technological improvements technological improvements, it is worth highlighting, above all:
- Breaking Java monoliths on Docker and Kubernetes without code rewriting.
- Improved resilience of services, thanks to the use of circuit breakers and distributed cache.
- Performance optimisation through building to native hardware container architecture.
- Drastic reduction of construction and deployment times .
It is also important to highlight methodological improvements that increase the productivity of the developments thanks to the fact that it is possible for different squads to work in parallel on the same monorepository of the final solution.
Dashboards and performance graphs updated in real time have also been created to increase the productivity of the solution's operation.
The result
The benefits of the final solution developed are manifold, including the following:
- Unified view of data and interactions through different channels.
- Scalability and monitoring (AI OPs).
- Substantial increase in front-end performance due to the implementation of a new architecture.
- Bi-directional and asynchronousdata activation.
The key success factors of the project have been, among others:
- To provide development teams with a set of technologies, tools and documentation to develop frontend and backend projects under standards and best practices.
- Front-end technological evolution, through migration to modern versions of development frameworks (Angular 15, Capacitor 5, Nx monorepo).
- Creation of achievable microfrontends.
- Backend migration to microservices on Cloud AWS.
One of the major productivity gains for the future is the fact that we have realised, during the migration, a large part of the functional modules of METS on a basis that allows them to be encapsulated in libraries and microfrontends, thus evolving them into true digital components that can be consumed by other applications, both MAPFRE's and those of third parties.