Choose your first consumer
Start with one complete example, including its matching node configuration:
- Keep a price map in memory: query once, then follow. It reads a stable snapshot, applies subsequent changes, and handles a reset.
- Keep application data across restarts: consume into PostgreSQL. It creates the destination tables, commits changes and their cursor together, then acknowledges Leani. The guide includes a restart check.
The historical windowed.toml quickstart retains query results with delivery
disabled. Use the configuration supplied by the consumer example; attaching a
consumer to that query-only node is unsupported.
A durable consumer is a named destination with a cursor and a lease. Its acknowledgement tells Leani what the destination has committed. For the full protocol and a reusable destination interface, see consume changes durably.