Rolling vs Blue-Green for Zero-Downtime Meteor Migration

Meteor Migration Trade-Off

The goal is a zero-downtime migration for a small Meteor application.

Constraints and Uncertainty

The choice is between rolling deployment requiring dual-schema support or blue-green deployment necessitating duplicate infrastructure.

Meteor's DDP lifecycle lacks a built-in mechanism to gracefully drain active in-flight method calls during a traffic cutover.

• How should application logic manage in-flight methods during cutover?
• Does DDP version pinning guarantee graceful transition for existing connections?