Data & Analytics Skill
Airflow DAG Patterns
Build production Apache Airflow DAGs with best practices for operators, sensors, testing, and…
$15
Database Migration
Execute database migrations across ORMs and platforms with zero-downtime strategies, data…
A cross-ORM, cross-platform guide for executing database migrations safely: across Sequelize, TypeORM, and Prisma: with zero-downtime strategies, data transformations, and tested rollback procedures. It teaches the expand-contract pattern so schema changes never take the application down, and wraps changes in transactions and checkpoints so nothing is left half-applied.
$15 one-time
Add to a kit → Prices include 20% VAT. · Forged on real agency work · one-time, no lock-in
- Type Skill
- Category Data & Analytics
- Delivery Email · instant
- License One-time
Inside the run · no black box
See the actual work before you buy it.
Schema changes are treated like surgery here: small incisions, a tested rollback for every cut, and a backup taken before production is touched. Expand-contract keeps the database live while the change lands.
- Cuts the change into single-responsibility migrations: ten column changes never share one file, because if the seventh fails the first six must roll back too; small migrations mean a small blast radius and a fast revert.
- Writes every up() with a symmetric down() and idempotency guards (IF EXISTS, IF NOT EXISTS, column presence checks), so a migration can be re-run after an emergency rollback without erroring out.
- Runs destructive or multi-step changes inside a transaction, and respects the engine difference: PostgreSQL DDL is transactional, MySQL DDL commits implicitly, which changes the safety plan on cross-database work.
- Uses expand-contract for zero downtime: add the new column, backfill, deploy code that writes to both, deploy code that reads from the new one, and only then drop the old column in a separate later migration.
- Takes a checkpoint before production: a backup table or a full dump created first, the migration verified with a count query afterwards, and on failure the table is restored from the backup instead of hoping down() works.
- Adds defaults before NOT NULL constraints, handles NULLs explicitly in data transformations, and tests the rollback path on staging, because an untested down() is not a rollback plan.
One power source. 6 lines out.
database-migration · core
core active · 6 lines
- ✓ renaming or retyping a c…
Renaming or retyping a column on a large table without downtime
- ✓ migrating schema or data
Migrating schema or data between ORMs (Sequelize, TypeORM, Prisma)
- ✓ splitting one column into
Splitting one column into several with a complex data transformation
- ✓ running a blue-green dep…
Running a blue-green deployment with a backward-compatible schema
- ✓ handling dialect differe…
Handling dialect differences when migrating between PostgreSQL and MySQL
- ✓ building checkpoint-base…
Building checkpoint-based rollback with backup tables and verification
Yours to keep.
Drag time forward. Watch what stays.
Forever
That's what owning means.
The rented stack
ai writing tool: subscription
expired · access lostanalytics suite: subscription
expired · access lostdesign platform: subscription
expired · access lost(nothing left)
Your forge
-
Change production schemas with zero downtime using the expand-contract pattern
license: perpetual -
Recover safely from a failed migration with transaction wrapping and checkpoint backups
license: perpetual -
Avoid data loss by handling NULL defaults, foreign keys, and verification correctly
license: perpetual -
Reduce blast radius by splitting big changes into small, independently reversible steps
license: perpetual
subscriptions expire · deeds don't
Everything in the box.
Pick a piece up. Watch it work.
Side-by-side migration examples for Sequelize, TypeORM, and Prisma
6 parts · one working system · ships instantly by email
This wasn't forged for everyone.
- Not for you if you'd rather rent a tool than own one.
- Not for you if you want someone else to run your stack.
- Not for you if you're happy guessing.
Backend developers and DBAs running schema or data migrations who need zero downtime and reliable rollback.
then this was forged for you.Works with
Universal by design: these run in any AI. Delivered in the open Agent Skills + MCP format (native in Claude); ChatGPT, Gemini, Cursor and Copilot adapt the same files their own way.
- Claude Native format
- ChatGPT Adapts via open standards
- Gemini Adapts via open standards
- Cursor Adapts via open standards
- Copilot Adapts via open standards
Catch what's on your mind.
the air is clear. nothing between you and the forge.
catch a spark: the forge will answer
-
We use a different ORM than the three named. Are these strategies still usable?
The expand-contract pattern and rollback discipline are ORM-agnostic, so the strategy carries even where the named examples for Sequelize, TypeORM, and Prisma do not match your tool. You translate the mechanics; the safe sequence stays the same.
-
Does expand-contract really avoid downtime, or just shorten it?
Done in order, expand then migrate then contract, the app keeps reading and writing throughout, so there is no required outage window. The trade is that you live with both the old and new shapes for a stretch, not that you accept a short downtime.
-
Does it run the migration against production for me?
It is a strategy and rollback guide, not an automated runner, so you execute the steps on your own infrastructure. A large data backfill still takes the time and compute your table size demands, regardless of how clean the plan is.
-
How is it delivered?
By email right after purchase: ready to run, downloaded instantly, no setup wait.
-
One-time or subscription?
A one-time purchase; no subscription or hidden fees. VAT (20%) is included.
-
Can I get a refund?
As a digital product, it can’t be refunded once downloaded. That’s why we show exactly what’s inside and who it’s for, right here.