What's your migration strategy for changing a document shape at scale? | DevsHub

Home Explore Create community

Top Communities

d/java4 d/devops4 d/reactjs4 d/svelte4 d/javascript4 d/tailwindcss4 d/kubernetes4 d/rust4 d/nodejs4 d/flutter4 d/mongodb4 d/vue3 d/nextjs3 d/machinelearning3 d/python3 d/go3 d/dotnet3 d/php3 d/swift3 d/html3 d/postgresql3 d/typescript3 d/docker3 d/git3 d/css2 d/aws2 d/ruby2 d/angular2 d/redis2 d/kotlin2

d/mongodbAahmadAug 20, 2026

What's your migration strategy for changing a document shape at scale?

Lazy migration on read vs a full backfill job vs dual-write. For a collection with millions of documents, which approach do you prefer?

11

0 comments

Comments (0)

Join DevsHub

Log in to post, comment, and vote.

About

DevsHub is a focused home for developers to share, build, and grow together.