Once a month, we send out top stories (like this one) along with Retool tutorials, templates, and product releases.Ī common migration pitfall for Sequelize + Postgres users Subscribe to the Retool monthly newsletter For these customers, we have to ship database migrations that can safely run automatically in any number of environments. On-premise customers run Postgres themselves, and Retool engineers don’t have access to these databases. It’s also important to note that we package Retool up in two ways: a cloud SaaS application and an application our enterprise customers can run inside their own networks, like Sentry or GitHub Enterprise. We use Sequelize as an ORM to communicate with Postgres. ![]() We’ve got a pretty standard Javascript-centric tech stack, with a Typescript + React + webpack frontend, a Node + Express backend, and a Postgres database server. Every company builds employee-facing tools to support important work, and our platform provides a drag-and-drop interface to quickly build, integrate, and use internal tools. Our team of about 25 Retool engineers are focused on building the fastest way to build internal applications. ![]() This post will highlight key lessons learned and what you can do to avoid making the same mistakes. Over the last 3 years, our team at Retool has navigated a few pitfalls and fixed major issues related to migrations in Postgres. And every time your app goes down, so does customer trust and revenue. A few weeks ago, I unintentionally took Retool down for 2 minutes when an out-of-control database migration tried to rewrite a mission critical data table.Īs my teammate and I cleaned up the mess-caused by incorrectly using transactions in the migration-I reflected on my last few years working with Postgres (officially PostgreSQL) and the different lessons I’ve learned when it comes to writing a safe database migration.ĭatabase migrations aren’t easy a migration that runs totally fine on your laptop may cause problems in production due to increased data and traffic volumes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |