You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 16, 2024. It is now read-only.
Right now the interface is too specific and tight to the concept of a cluster,
we should maybe revisit that and make it so its more tight to the message instead.
We could align more to the api style of effect/platform's KeyValueStore. (and cluster-platform could provide a storage backed on that)
API would look like:
Need to experiment because I am not a fan of generics in services, but I could see that being nicer dx wise.
exportinterfaceAtLeastOnceStorage<MsgextendsMessage.Message.Any>{readonly[AtLeastOnceStorageTypeId]: AtLeastOnceStorageTypeId/** * Stores a message into the storage, eventually returning the already existing message state as result in the storage */upsert<MsgextendsMessage.Message.Any>(message: Msg): Effect.Effect<void>/** * Marks the message as processed, so no more send attempt will occur */markAsProcessed<MsgextendsMessage.Message.Any>(message: Msg): Effect.Effect<void>/** * Gets a set of messages that will be sent to the local Pod as second attempt */sweepPending: Stream.Stream<Msg>}
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Right now the interface is too specific and tight to the concept of a cluster,
we should maybe revisit that and make it so its more tight to the message instead.
We could align more to the api style of effect/platform's KeyValueStore. (and cluster-platform could provide a storage backed on that)
API would look like:
Need to experiment because I am not a fan of generics in services, but I could see that being nicer dx wise.
The text was updated successfully, but these errors were encountered: