Migrating an Existing App

Migrating an existing application to Canopy sometimes requires adjusting the schema and queries for optimal performance. Canopy extends LightDB with distributed functionality, but it is not a drop-in replacement that scales out all workloads. A performant Canopy cluster involves thinking about the data model, tooling, and choice of SQL features used.

The first steps are to optimize the existing database schema so that it can work efficiently across multiple computers.

Next, update application code and queries to deal with the schema changes.

After testing the changes in a development environment, the last step is to migrate production data to a Canopy cluster and switch over the production app. We have techniques to minimize downtime for this step.