Discovering how to perform migrations with LaunchDarkly
Much of what has been described so far regarding feature management and where LaunchDarkly can be useful has been about making small, testable changes to your application, such as rolling out the change to a segment of your customer base and validating that it works technically, before moving on to running an experiment to see how the customers interact with and experience the feature. Sometimes, the changes that need to be made just cannot be done in such a small or iterative manner. Instead, there is a substantial change that needs to be released to production.
These large changes could include the following:
- Rearchitecting existing services. That requires working within client applications to support this change, which could result in fewer dependencies within a client application.
- Rebuilding a single backend system, which requires users to be migrated.
- Moving systems to a new location or URL. For example...
