Remote / An event-sourced domain behind Remote
Limits
- A beta, pinned. The adapter relies on behaviour of
@alchemy.run/domain@2.0.0-beta.86that its owntest/domain/behaviour.test.tsrecords, and breaks when a release changes it. - Tested in memory and over local HTTP. Nothing here is deployed; Domain's Durable Object hosts and WebSocket protocol are not exercised.
- Not exercised: evolving an Event's schema, and models with Policies or Sagas. The adapter reads Views and sends Commands and has no part in either, but no test here runs one.
- Lists are a paged Domain Query's, read forward; relations are
onerelations held as ids. The README's "Lists and one relations" has the detail. - It is not a second layer over a Remote server. A page reaches one
authority or the other. And it does not use
@alchemy.run/domain/Foldkit, which folds Domain state into Model fields of the application's own: besideRemote.Modelthat would be two owners of one row.
Where to go next
foldkit-remote-domain's README: every binding, lists,onerelations, first paint from a server render, the command id, and each failure in detail.examples/writes-domain: the model above with SQLite and memory beside it, deciding one write alike.- One domain declaration and Declared writes: the declarations this guide lowers.
- Alchemy Domain's own documentation for Aggregates, Views, Policies, Sagas and hosting.