Neon Twin: How to deploy a change tested in Neon to prod in RDS

In this article, we explored a workflow to test changes in a dev environment in Neon and push the changes to prod in RDS using database branching with Neon. We introduced the concept of database branching, which enables you to instantly create isolated copies of a particular dataset via copy-on-write, allowing you to safely experiment with changes without affecting the main development branch. The article also covered how to document changes made to your dev branches in Neon using schema diff feature and how to automate this process through GitHub Actions. Two methodologies were presented for migrating changes from your Neon Twin back to your AWS RDS production database: Using SQL Files and psql, and Using Prisma ORM. Both methods utilize GitHub Actions to trigger the migration process when a pull request is merged into main. The article concluded with setting up syncing production with Neon Twin using a similar approach as before but rather than on a schedule it will run after production migrations have been applied.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.