Introducing Temporal Resources
2026-10-31
![]()
Temporal resources, an experimental Ash feature, let an application read and write its state at any point in time, past, present or future, without changing ordinary application code. Four lines of configuration add a valid_at period to each record, and an as_of option queries the data as it stood at a given moment, on standard tables. The post sets it against paper trails, event-driven design and event sourcing: here, history is queryable with ordinary filters and relationships, retroactive changes are possible, and so are updates scheduled for the future.
Was this useful?