#elarion

What the actor model guarantees, when a table beats an actor, and how far one mailbox and a single PostgreSQL row can carry you. No Orleans or Akka required.

Cache, fan-out, job coordination, leader election, idempotency: running all of it on the one PostgreSQL you already operate, and why SKIP LOCKED is the one pattern deliberately avoided.

One attributed class becomes a DI registration, an HTTP endpoint, a JSON-RPC method and an MCP tool at build time. What it buys and what it costs when source generators carry the whole architecture.