Introduction
At Vocento, we faced the challenge of migrating User Platform and all systems to a new user identity provider, where we had to incorporate a novel user model and a fresh backend and frontend Framework.
- The migration of the user frontend layer involved revamping an outdated JavaScript project burdened with technical debt accumulated over more than 10 years and thousands of lines of code.
- For the backend user layer migration, we dealt with a suite of projects encompassing over 300 endpoints with varied functionalities.
My role and contributions
- As a Principal Software Engineer, I directed and managed the backend and frontend teams, comprising 20 professionals.
- I led the analysis, architecture, design, documentation, development and quality assurance of new, highly scalable cross-functional solutions for backend and frontend, utilizing industry best practices: Microservices, Hexagonal Architecture, Domain-Driven Design, and TDD.
How we did it
The user frontend JavaScript framework was developed using JavaScript, React, and Webpack, employing Hexagonal Architecture with the following layers:
- Domain, Transformers, Application (Use Cases), Infrastructure (Services), etc.
The Microservices solution was crafted using PHP, Symfony, and OpenAPI, implementing the following architecture:
- A new User Domain featuring the required domain models, value objects, DTOs, transformers and events.
- A novel cross-functional Service Layer project adding extra abstraction to prevent direct connections to the provider.
- A new cross-functional standalone PHP client library component and a Symfony bundle facilitating connection to the Service intermediary layer through Domain and Request, enabling easy installation and usage across any project.
What we achieved
We developed a scalable, cross-functional solution by creating a new User JavaScript Framework that manages user interactions across all Vocento pages, including identity flows, login, registration, user profile, social networks, purchases, and interactions with other business products. This User JavaScript Framework allows integration with the new provider and provides functionalities like public and private APIs, a client for user Microservices, User Domain, Business Use Cases, management of public and private Events and Promises, Dependency Management, Product Management, and independent dynamic compilation for WPO optimization.
The backend Microservices solution abstracts all the business logic required with the new provider, utilizing the functionality provided by the provider through a client, domain, and public Microservices API.
Challenges, difficulties and solutions
The project faced numerous challenges and difficulties, overcome thanks to the continuous effort of the teams involved and ongoing management with continuous communication.
As it impacted many of the company’s user systems, a thorough analysis of the migration strategy, constant planning, risk analysis, impact prevention, and continual coordination and communication with the teams were essential.
Motivation is critical in a long-term project
-
As a Technical Lead, I tackled the challenge of leading, mentoring, and motivating 20 individuals with diverse roles and profiles, developing a set of cross-functional solutions and technical architectures that enabled agile development and maximum scalability.
-
One of the greatest challenges was maintaining the quality of solutions without impacting the development timeline of the migration project. Another significant challenge was the correct allocation of time with the teams, prioritization, daily coordination, and assignment of user stories and tasks to each team member.
-
Another complex challenge was the existing technical debt in some systems for over 10 years, and the heavy dependency on the current user identity provider.
Results
The new Frontend User Framework enables agile and scalable development of multiple solutions, products, and business requirements. We conducted unit and application testing to ensure solution quality. We achieved over an 80% reduction in technical debt compared to the previous solution, starting from a new, optimized frontend solution for WPO.
The new backend layer and cross-functional components facilitated the easy and standard migration of the existing 300 endpoints for adaptation to the new provider, in addition to enabling a new Microservices project abstracting the connection with the new provider.
Conclusion
Despite being a highly complex and uncertain project, involving multiple systems and teams, the outcome was highly satisfactory. This success was achieved through the use of best practices in team management, continuous communication, and the design of systems with scalable architectures. These solutions will endure for many years, enabling extremely agile development for any new team member and meeting the business needs of the company.
This project would not have been possible without the excellent work carried out by the members of the frontend and backend user teams, with whom I am proud to have worked over these years, developing a strong bond of friendship.