This website uses cookies to ensure you get the best experience.
Learn more.
A migration project discovers that several applications share one database. What should wave planning account for?
Published
- Duplicate the database without planning which copy accepts writes.
- Shared schema dependencies, transaction behavior, coordinated change, and intermediate connectivity.
- Assume separate hostnames imply completely independent state.
- Migrate applications alphabetically regardless of dependencies.
Comments — 0
Sign in to comment