Cloud migration
User-driven SaaS migration with zero downtime
- Area
- SaaS platforms
- Customer
- Quadient
An administrator could choose when to move to a higher version or a more powerful node without interrupting users' work.
0planned outages
Scoperollbackpart of the migration procedure
Starting point
What needed to change
Data had to be moved between cluster nodes under full load, ongoing changes had to be preserved, and a safe way back had to remain available.
Our responsibility
How we approached the solution
We used event sourcing, a snapshot and temporary routing of events to both the old and the new node. After synchronisation we switched the routing in Kafka.
Part of the delivery
A complete scope
- Snapshot and data synchronisation
- Parallel event routing
- Routing switchover
- Rollback and data upgrade
Impact
What the customer gained
- Users could work with the application throughout the move.
- The customer chose a suitable moment for the migration.
- A return to the original version was part of the procedure.
Technologies and approaches
- Event Sourcing
- Kafka
- Snapshot
- Cloud cluster