It’s different to Spanner. Materialize uses “virtual” (Lamport-style) clocks to version data, basically more like transaction ids than a physical time. The vers

It’s different to Spanner. Materialize uses “virtual” (Lamport-style) clocks to version data, basically more like transaction ids than a physical time. The versions of different data are compared in such a way that outputs are always strongly consistent (though eventually consistent). This is more complex than it sounds when you include disparate input sources, calculations that may be recursive (and distributed), etc.