umzug VS sequelize-typescript

I like to use plain SQL files for migrations but needed a tool to handle this. Settled for Umzug in the end, which is working pretty well. Its high configurable and framework-agnostic.

If we want to change the settings for this table (such as the BillingMode) or define additional Global Secondary Indexes, we can use migrations when required. In the example project, I configured migrations using Umzug. This required simply to define a DynamoDB storage for Umzug: umzugDynamoDBStorage.ts.

Read up on migrations. Sequelize uses the Umzug environment.

Sequelize docs suggest Umzug

I am using sequelize. Works decent. https://github.com/sequelize/sequelize-typescript

But in my opinion all that changes with the existence of the sequelize-typescript dependency. The way the entities are structured and the way the connection to the database is made becomes much more intuitive. This experience is ideal because you can transition from JavaScript to TypeScript in a much more convenient way and without changing the stack.

Grouparoo uses the Sequelize Object Relational Mapper, or ORM, along with sequelize-typescript so we can work with the same Objects in our codebase, regardless of the database providing persistence. Sequelize does a great job of abstracting away the differences between the database types... most of the time. In this blog post, I’ll be sharing the times when the differences in the SQL implementations of Postgres and SQLite matter.