GET API calls to object storage.
Reading data relies on a combination of domain-specific logic as well
as shared storage access primitives. Each database implements its own
indexes and data layouts for optimal read performance, but all use
SlateDB queries to access the data through multiple levels of caches.
Read Freshness
Read freshness can be measured in terms of object storage round trips between a write being accepted and it being visible to a query:
Each round trip typically adds around 100ms of latency plus the polling
interval, which is configurable. In practice, the polling interval dominates
the freshness delay.