Real-Time Serving Layer
Where a low-latency read of a streaming aggregate actually lands.
5 to work through
-
intermediate Multiple choice
A product page needs the current computed price for one product id at 40,000 reads per second with p99 under 25 ms. A stream processor already recomputes each product's price every few seconds from competitor and inventory events. Where should the read path go?
3 min answer -
advanced
A contest platform must update leaderboards for millions of participants as scoring events arrive. What is the architecture, and what must not be attempted?
2 min answer -
advanced
A feature needs personalised results in under 50 ms for millions of users. What is computed when?
2 min answer -
advanced
A flash sale opens at a published time. The precomputed inventory and price data is served from a real-time serving layer whose caches were rebuilt an hour earlier during a deploy. What happens in the first ten seconds after the sale opens?
3 min answer -
advanced
A real-time platform must serve computed state to a low-latency request path. What should the serving layer look like?
2 min answer
2 terms in this topic
Real-Time Serving Layer
The read path that answers queries in milliseconds from precomputed or continuously updated state — where the design question is what to compute when.
conceptServing Latency Budget
The end-to-end time from an event occurring to its effect being queryable, allocated across ingest, processing and serving.
Neighbouring topics
Streaming & Real-Time Data
General material on continuous processing of unbounded data.
Streaming vs Batch
The freshness requirement that actually justifies streaming, and the cost of assuming one.
Exactly-Once Semantics
What the phrase really means, where it holds, and the idempotent sink underneath it.
Stream Processing Frameworks
Flink, Kafka Streams, Spark Structured Streaming — state, checkpointing and recovery.
Windowing
Tumbling, sliding and session windows, and the aggregation each one answers.
Watermarks & Late Data
Deciding a window is complete when events can still arrive, and what to do when they do.
Stateful Stream Processing
Keyed state, state backends, checkpoint size, and the restore time that follows.
Stream-Table Duality
A changelog and a table as two views of the same thing, and materialising between them.
Kappa vs Lambda
One pipeline replayed versus two pipelines reconciled, and the maintenance each carries.
Streaming Schema Evolution
Changing an event's shape while a retained log still holds every older version of it.
Streaming Joins
Joining two unbounded streams, the buffering it needs, and the enrichment alternative.
Backfill & Reprocessing
Replaying history through changed logic without double-counting the live output.
CDC to Stream
Turning database changes into an event log, and how that differs from a domain event.
Feature Freshness
How stale a feature can be before the model degrades, and the pipeline that follows.
Streaming SLOs
End-to-end latency, consumer lag and completeness as commitments rather than dashboards.
Partition Keys & Ordering
Ordering guaranteed only within a partition, and choosing the key that makes that enough.
Dead Letter Handling
The poison message that blocks a partition, and the queue nobody reads.
Streaming Cost
Always-on compute, retention and cross-zone traffic as the three bills that surprise.
Real-Time Analytical Stores
Druid, Pinot and ClickHouse — ingest-and-query engines for sub-second aggregation.