Back to problems

Event Ingestion + Top-K Aggregation

System Design · Oracle · Hard

Requirements Initial design: one machine accepts event submissions from clients. Increased demand: traffic has expanded by several orders of magnitude, so the one-server choke point needs to be eliminated. New functionality: support top-K computations across incoming events, such as the most frequent event categories, clients, or resources. Interview timing: 45 minutes, following a 10-minute behavioral introduction. Scalable event ingestion and top-K processing pipeline…

Checking your access…