effect-pubsub-event-bus

What problem does it solve?

Effect developers need a reliable way to coordinate publish/subscribe communication without messy callback lifecycles, untyped payloads, or manual cleanup that can cause leaks and inconsistent shutdown behavior.

Core Features & Use Cases

• Typed event definitions: Use discriminated unions with Schema.TaggedClass so publishers and subscribers agree on payload shape.
• Stream-based subscriptions: Turn PubSub channels into composable Streams via Stream.fromPubSub, enabling filtering, mapping, and backpressure behavior.
• Scoped, automatic cleanup: Use Effect.forkScoped and finalizers to ensure subscriptions and PubSub shutdown happen when the owning Scope ends.
• Event-driven service architecture: Replace imperative event buses with reactive, stream-first designs for inter-service domain events.

Quick Start

Implement an event union with Schema.TaggedClass, create a Bus Layer that uses PubSub plus Stream.fromPubSub, and subscribe with forkScoped so cleanup is tied to the layer scope.