Legacy modernization
Modernising the NoSQL layer of a large product
- Area
- SaaS platforms
- Customer
- Quadient
The database layer changed in a single coordinated release, without the modernisation adversely affecting users.
Scope≈ 50,000files in the source code
Scope50developers working concurrently
Scope1 releasecoordinated deployment
Starting point
What needed to change
Database access ran through tens of thousands of files, while another fifty programmers were contributing to the product at the same time. The change could not be released in small parts.
Our responsibility
How we approached the solution
We rewrote the database layer, split the legacy code into smaller parts and prepared a coordinated integration of the changes into a single product release.
Part of the delivery
A complete scope
- Dependency audit
- New database layer
- Legacy code refactoring
- Coordinated release
Impact
What the customer gained
- The product gained a modern way of working with data.
- The original functionality was preserved.
- The changes were synchronised with the parallel work of other teams.
Technologies and approaches
- NoSQL
- Refactoring
- Legacy modernization
- Git