Migrate from API Keys with Zero Downtime

The Migration Problem

Ripping out API keys and replacing them with a new auth system sounds terrifying. You're managing 50+ microservices in production. You can't afford downtime. You can't migrate everything at once.

Traditional migrations force an all-or-nothing cutover. You set a maintenance window, update every service, hope nothing breaks, and pray you didn't miss a dependency.

xLink's Dual-Mode Solution

Run both systems simultaneously. xLink's DualModeAdapter accepts BOTH API keys and DIDs. Your services migrate one at a time, at your own pace, with zero downtime.

4-phase migration strategy:

Phase 1 - Add xLink: Deploy xLink alongside existing API keys (15 seconds per service)
Phase 2 - Test in parallel: Route 5% of traffic through xLink, monitor for issues
Phase 3 - Gradual rollout: Increase to 25%, 50%, 75% as confidence grows
Phase 4 - Deprecate keys: Remove API key code once 100% traffic on xLink

Each service migrates independently. If something breaks, roll back that one service. Everything else keeps running.

Canonical Code — xLink Zero-Config Connect

const conn = await connect('payments')
await conn.value.agent.send({ to, payload })

Deep Dive: Migration Patterns & Production Stories

Step-by-step migration guides, dual-mode architecture, rollback procedures, and production case studies.

Read White Paper →