Repository navigation
feat(rivetkit): add experimental effect cluster support - #6023
Closed
NathanFlurry wants to merge 1 commit into
Closed
NathanFlurry wants to merge 1 commit into
NathanFlurry wants to merge 1 commit into
Conversation
NathanFlurry
force-pushed
the
task-20261115-142645-7dc6d2e2
branch
from
November 22, 2026 03:14
6c43df2 to
f23ddfc
Compare
Member
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Experimental Effect Cluster support on Rivet Actors, as a new
@rivetkit/effect-clusterpackage.Sharding,WorkflowEngine, andPersistedQueueFactoryservices on Rivet Actors; existing Effect Cluster code runs unchangedClusterCronon a singleton actorDeliverAtand durable clocks use actor schedules, with a recurring heartbeat that replays missed workActorSqlClientgives each entity its own SQL database, committed in the same transaction as its mailboxactionTimeout(default 15 minutes) fails, andPersistedQueuecleanup is not supported yetArchitecture
Each entity, workflow, queue, and singleton runs as its own Rivet Actor:
A persisted ask is one action through the gateway; the request and reply are stored in the actor's own SQLite:
Compared with Effect's SQL backend, which coordinates runners through a shared Postgres with a 300-shard hash ring and advisory locks: