Rebuilding a Data Platform Under Continuous Writes
A database migration becomes a distributed-systems problem as soon as the application must keep accepting changes. A bulk copy can move records, but it cannot determine which writer is authoritative, whether a delayed event is still valid, or what happens when a successful write loses its response. Those questions define the project more precisely than the choice of destination database. Consider a multi-tenant service whose read path assembles frequently requested objects from several document collections. Background imports compete with interactive requests, and a small engineering team operates the storage stack. The redesign separates authoritative records from query projections, moves the primary access path from MongoDB to DynamoDB, and uses Redis selectively for reusable computation. ...