Migrate from Bee-Queue to glide-mq

When to Apply

Use this skill when:

• Replacing bee-queue with glide-mq in an existing project
• Converting Bee-Queue's chained job API to glide-mq's options API
• Updating connection configuration from ioredis to valkey-glide
• Upgrading from bee-queue due to Node.js compatibility or maintenance issues

Step-by-step guide for converting Bee-Queue projects to glide-mq. Bee-Queue uses a chained job builder pattern - this migration requires rewriting job creation and separating producer/consumer concerns.

Why Migrate

• Unmaintained - last release 2021, accumulating Node.js compatibility issues
• No cluster support - cannot scale beyond a single Redis instance
• No TLS - requires manual ioredis workarounds for encrypted connections
• No native TypeScript - community @types/bee-queue only, often outdated
• No priority queues - workaround is multiple queues