(
service: string | { readonly key: string },
entry: { readonly nodeKey: string }
): Effect.Effect<string, never, Advice>Prefer a directory row's nodeKey for a HyperService.
const rows = yield* Lookup.nodesServing(Worker)
yield* Lookup.preferEntry(Worker, rows[0]!)export const const preferEntry: (
service: string | { readonly key: string },
entry: { readonly nodeKey: string }
) => Effect.Effect<string, never, Advice>
Prefer a directory row's nodeKey for a HyperService.
const rows = yield* Lookup.nodesServing(Worker)
yield* Lookup.preferEntry(Worker, rows[0]!)
preferEntry = (
service: | string
| {
readonly key: string
}
key: stringkey: string },
entry: {
readonly nodeKey: string
}
nodeKey: stringnodeKey: string },
): 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<string, never, class Adviceclass Advice {
key: Identifier;
Service: {
advise: (payload: { serviceKey: string; prefer: string }) => Effect.Effect<string, never, never>;
clear: (payload: { serviceKey: string }) => Effect.Effect<boolean, never, never>;
preferred: (payload: { serviceKey: string }) => Effect.Effect<Option.Option<string>, never, never>;
};
}
Lookup placement board — coordinator advice for nodeless /
Hyperlink.lookupClient
dial.
v1: last-write-wins, in-memory, no advisor ACL. Algorithms stay app-owned (who calls
advise
); Lookup only stores and surfaces the preference.
Advice> =>
const advise: (input: {
readonly serviceKey: string
readonly prefer: string
}) => Effect.Effect<string, never, Advice>
Publish placement advice (requires
Advice
in context).
yield* Lookup.advise({ serviceKey: Worker.key, prefer: "fleet/Worker#w2" })
advise({ serviceKey: stringserviceKey: const serviceKeyOf: (
service:
| string
| {
readonly key: string
}
) => string
Tag or wire key → serviceKey string.
serviceKeyOf(service: | string
| {
readonly key: string
}
prefer: stringprefer: entry: {
readonly nodeKey: string
}
nodeKey: stringnodeKey });