The service shape: append an (already-encoded) entry to a stream, and read a stream back. Entries
are opaque (unknown) — callers encode/decode with their own schema; the store just persists.
export interface HistoryStoreShape {
readonly HistoryStoreShape.append: (streamId: string, entry: unknown) => Effect.Effect<void>append: (streamId: stringstreamId: string, entry: unknownentry: unknown) => import EffectEffect.interface Effect<out A, out E = never, out R = never>The Effect interface defines a value that lazily describes a workflow or
job. The workflow requires some context R, and may fail with an error of
type E, or succeed with a value of type A.
When to use
Use when you need to represent a lazy, composable workflow that can require
services, fail with a typed error, or succeed with a typed value.
Details
Effect values model resourceful interaction with the outside world,
including synchronous, asynchronous, concurrent, and parallel interaction.
They use a fiber-based concurrency model, with built-in support for
scheduling, fine-grained interruption, structured concurrency, and high
scalability.
To run an Effect value, you need a Runtime, which is a type that is
capable of executing Effect values.
Effect<void>;
readonly HistoryStoreShape.read: (streamId: string, options?: HistoryReadOptions) => Effect.Effect<ReadonlyArray<unknown>>read: (
streamId: stringstreamId: string,
options: HistoryReadOptionsoptions?: HistoryReadOptions,
) => import EffectEffect.interface Effect<out A, out E = never, out R = never>The Effect interface defines a value that lazily describes a workflow or
job. The workflow requires some context R, and may fail with an error of
type E, or succeed with a value of type A.
When to use
Use when you need to represent a lazy, composable workflow that can require
services, fail with a typed error, or succeed with a typed value.
Details
Effect values model resourceful interaction with the outside world,
including synchronous, asynchronous, concurrent, and parallel interaction.
They use a fiber-based concurrency model, with built-in support for
scheduling, fine-grained interruption, structured concurrency, and high
scalability.
To run an Effect value, you need a Runtime, which is a type that is
capable of executing Effect values.
Effect<interface ReadonlyArray<T>ReadonlyArray<unknown>>;
}