Additional transports: Kafka, Azure Service Bus, Redis Streams #267

Activity

1. adenhertog

   added this to the Phase 4: Ecosystem & platform milestone on Sep 30, 2026
2. adenhertog

   added

   enhancementNew feature or requestNew feature or request

   roadmapPart of the project roadmapPart of the project roadmap

   on Sep 30, 2026
3. adenhertog

   marked this as blocked on Sep 30, 2026

   • Handler and workflow test helpers #265
4. adenhertog

   marked this as blocking 3 issues on Oct 1, 2026

   • Quick-start tutorial and runnable examples/ with docker compose #252
   • Document features that exist but aren't in the docs #253
   • Docs: concepts page and comparison with Temporal, BullMQ and NestJS #254
5. adenhertog commented on Oct 7, 2026

   

   adenhertog

   on Oct 7, 2026

   ContributorAuthor

   More actions

   Split into one issue per transport, ranked by real-world use (.NET service-bus framework support, npm downloads), fit with the bus model, CI emulator availability and maintenance cost:

   Phase 4

   • Azure Service Bus transport #346 Azure Service Bus transport
   • Redis Streams transport #347 Redis Streams transport (replaces the stale node-ts/bus-redis)

   Backlog

   • Kafka transport #348 Kafka transport: blocked until a maintained Node client supports Kafka 4.2 share groups (KIP-932)
   • NATS JetStream transport #349 NATS JetStream transport
   • Google Cloud Pub/Sub transport #350 Google Cloud Pub/Sub transport

   Considered and skipped: Amazon EventBridge (an event router, not a queue; at most a future publish option on bus-sqs), ActiveMQ/Artemis, Azure Storage Queues (no pub/sub), MQTT and Pulsar (niche for this model).