Expand description

Materialize’s compute layer.


Code to spin up communication mesh for a compute replica. Most of this logic was taken from Timely’s communication::networking module, with the crucial difference that we actually verify that we can receive data on a connection before considering it established, and retry otherwise. This allows us to cope with the phenomenon of spuriously accepted connections that has been observed in Kubernetes with linkerd.
Worker-local state for compute timely instances.
An interactive dataflow server.


A TraceManager stores maps from global identifiers to the primary arranged representation of that collection.
Base metrics for arrangements.