Migrating six microservices onto a consolidated stack

XAND ran six Node.js microservices backed by MongoDB and PostgreSQL. The platform ran on Heroku, with AWS S3 for object storage. The decision was to consolidate onto a React and Laravel stack.

Six services meant six deployment paths, six sets of dependencies, and data split across two database engines. A migration like this fails in the seams: the half-moved data model, the service that still owns one write path, the cutover that has no way back. It has to be sequenced so the product keeps working at every step.

• › Planned and executed the migration of all six Node.js microservices onto the React and Laravel stack.
• › Handled the data across both MongoDB and PostgreSQL rather than forcing a single-engine rewrite.
• › Sequenced the work so the running product stayed available through the migration.

• › All six services migrated and consolidated onto one stack.

Similar problem?