Effect-TS / cluster

https://effect-ts.github.io/cluster

Effect-TS/cluster Issues

Provide Pods/ShardingManager/ShardingClient implementation that relies on effect/rpc
Closed 2 months ago
make SerializedEnvelope a Message itself
Closed 2 months ago
Do not recreate test container for each test
Closed 2 months ago
Fix Tag values
Closed 2 months ago2
Rewrite RecipientType to be effect/Data instead of interfaces
Closed 2 months ago
Consider renaming RecipientType to something better
Updated 2 months ago
MessageState: require MessageStateCompleted result instead of it being Optional
Closed 2 months ago
Consider defaulting sendMessage to indefinite retry
Closed 2 months ago
Consider renaming fromFunctionEffect to just "fromEffect"
Updated 2 months ago
Use PrototypeObject to assign TypeIds
Updated 2 months ago
Refactor data types to use schema classes
Closed 2 months ago
Refactor interface of AtLeastOnceStorage
Updated 3 months ago
Investigate storing release order of activities in cluster-workflows
Closed 3 months ago20
Align namings to Schema Encoded/Type
Closed 4 months ago
Use effect/PrimaryKey and @effect/schema/Serializable in the message protocol
Closed 4 months ago
Rename StorageFile to StorageFileSystem and rely on @effect/platform
Updated 4 months ago2
Investigate using TaggedRequest instead of Message since now that's a Schema supported type
Closed 7 months ago
Investigate if ReplyId is still need or we can put responses by reference to its message instance.
Closed 7 months ago1
Mark all methods in interfaces as readonly, and change from call signature to readonly property with arrow function
Closed 7 months ago1
Revise Sharding.live and ensure side effects like event hubs are started in a scope
Closed 7 months ago
Internalize all implementations like in other effect modules
Closed 7 months ago