As applications evolve and developers add new features, the structure of the backing database evolves as well. In LoopBack 3, we provided JavaScript API for automatic migration of database schemas. Recently, we improved LoopBack 4 to leverage these APIs and provide an easy-to-use database migration tool available from the command-line.

For example, when the developer adds a new property to a model, they also need to define a new column in their SQL database schema. NoSQL databases like Cloudant and MongoDB don’t require schema, but still require developers to define indices to speed up frequent queries.

Projects scaffolded with a recent version of our CLI tool lb4 come with a new package script that automates the database migration process.

$ npm run migrate

Under the hood, this script is a thin wrapper for a new Application API contributed by the RepositoryMixin: app.migrateSchema(). The method migrateSchema iterates over all datasources registered with the application and ask the underlying connector to migrate database schema. You can learn more in our Database migrations documentation, as well as the pull requests #2059 and #2094.

In the future, we want to implement a more robust migration framework that will empower the developers to fully control database commands executed during the migration. We would like to work on these improvements together with our community, so we encourage you to join the discussion in GitHub issue #487

Call to Action

LoopBack’s future success depends on you. We appreciate your continuous support and engagement to make LoopBack even better and meaningful for your API creation experience. Please join us and help the project by: