Stores and named stores

JobStore is a yieldable better-effect Service. Its structural Contract contains atomic operations for enqueue, claim, fenced settlement/release, heartbeat, stalled recovery, wake, inspection and administration. The core never sees SQL, Redis keys, connection objects or driver-specific DTOs.

import { Layer, Runtime } from 'better-effect'
import { JobStore, MemoryJobStore, Queue } from 'better-effect-mq'

declare const adapter: JobStore.Contract
const Durable = JobStore.named('durable')
const DurableLayer = Layer.succeed(Durable, Durable.of(adapter))

Bind a Job explicitly when several stores share one Runtime:

import * as z from 'zod'
import { Codec, JobEncodeFailure } from 'better-effect-mq'
import { Schema as CoreSchema } from 'better-effect-schema'
import { Schema } from 'better-effect-schema/zod'

const AuditPayloadSchema = z.object({ event: z.string().min(1) })
class AuditPayload extends Schema.Class<AuditPayload>('app/AuditPayload')(AuditPayloadSchema) {}
const AuditPayloadCodec = Codec.standardSchema({
  schema: AuditPayload,
  encode: (value) =>
    CoreSchema.encode(AuditPayload, value).mapError(
      (error) => new JobEncodeFailure({ message: error.message, code: 'schema-encode' })
    )
})
const AuditJob = Queue.define('audit').job('write', {
  version: 1,
  payload: AuditPayloadCodec,
  store: Durable
})

The default MemoryJobStore is an isolated in-process reference driver. It is useful for tests and local demos, not for durable or cross-process delivery. MemoryJobStore.layer creates fresh state per Runtime; make creates one explicit instance. MemoryJobStore.layerFor(namedToken, options) supplies a named binding.

const runtime = await Runtime.make(
  Layer.merge(MemoryJobStore.layer, MemoryJobStore.layerFor(Durable))
)

Adapters must preserve claim ordering, lease fencing, atomic settlement, request timestamp validation and wake correctness. Capability flags can optimize polling but cannot weaken those semantics. See the advanced storage adapter guide.