Events and workflows

Carry typed domain events, operation context, transactional delivery, and replay-safe processing across application boundaries.

Supported approaches

Domain events

available

Emit typed facts with correlation, causation, actor, scope, and trace context.

Packages

@playstack/events@playstack/nest-events

Frameworks and integrations

Event storage and replay

available

Persist ordered streams and expose replay through explicit storage and framework adapters.

Background jobs and workflows

available

Dispatch validated, retry-aware jobs through a portable queue contract and serve them from the application edge.

Frameworks and integrations

integration

Queuebert

Connect existing named BullMQ queues to an application-authorized Queuebert installation.

framework

Next.js

Compose Playstack server contracts, React bindings, SSR handoff, and route adapters at the Next.js application edge.

framework

NestJS

Connect portable Playstack capabilities to dependency injection, guards, decorators, request context, workers, and lifecycle hooks.

integration

Prisma

Persist Playstack capabilities through explicit application-owned Prisma clients, transactions, and managed schema fragments.

integration

BullMQ

Dispatch and process typed Playstack jobs through BullMQ with explicit Redis ownership and native queue access.

integration

Inngest

Dispatch portable Playstack queue jobs through Inngest and serve the generated functions from Next.js, NestJS, or another supported framework.

integration

Cloudflare Queues

Typed Worker jobs with per-message acknowledgements, bounded batches, retries and explicit terminal-failure handling.

framework

Cloudflare Workers

Run portable contracts in Web-standard runtimes with explicit Workers KV, R2, Queues and Durable Object adapters.

Package reference

@playstack/events

Events connect capabilities

Typed events let packages remain focused while applications decide what must happen synchronously, transactionally, or after commit.

Context survives the boundary

Operation context makes causation and observability explicit rather than rebuilding it independently in every transport.

Queue work behind the same boundaries

@playstack/queues carries typed jobs, retry policy, terminal-failure hooks, and trace context into background execution. The Inngest adapter can serve the same job definitions from Next.js or NestJS while leaving provider-specific workflows accessible through the native client.

The Cloudflare Queues adapter now handles Worker producer/batch boundaries. It acknowledges successes individually and requires durable terminal-failure handling before acknowledging poison messages. It does not implement BullMQ's progress, scheduling or administration surfaces.

Go

Playstack Pro tag
OriginsPricingBlogNewsletterChangelogStatusRoadmap
ContributorsCommunityIn Use ShowcaseCase StudiesPartnersSponsors
FAQsSupportContact

© 2026 Playstack. All rights reserved.

With OSS
Terms of ServicePrivacy PolicyCookie PolicyImprint

By

Commune Software