A stateful stream processor: dataflow graphs, keyed state in RocksDB, event time and watermarks, windows, barrier checkpoints, exactly-once into Kafka.
Data engineers building storage, streaming and processing systems.
Your approach: Use diagrams or prose for data contracts, state ownership, throughput, ordering and recovery where the brief requires them.
Design a Stream Processor like Flink. A stateful stream processor: dataflow graphs, keyed state in RocksDB, event time and watermarks, windows, barrier checkpoints, exactly-once into Kafka. Work from the scoping questions below. State assumptions for any unspecified load, guarantee or target, then trace your design end to end. Explain one difficult case and a credible alternative; the worked example is a reference, not a required implementation.
Resolve the scoping questions for a Stream Processor like Flink. Separate stated behavior from assumptions, and identify what is outside your design.
Declare relevant volume, latency, freshness, quality or cost targets with units. Show calculations or an evaluation plan that can test them; unspecified targets are your assumptions, not hidden pass criteria.
Explain how your guarantees hold in a difficult case relevant to this subject. Address: Upgrades without losing state? Rescale later?
Identify users, required behavior and exclusions. Answer: What runs on it? How big?
Define the information owned by the system and the inputs, outputs and errors at its boundaries. Resolve: Exactly-once where? How late can clicks be?
Estimate the dominant workload and resource demand with units and explicit assumptions. For a learned system, also state how quality is measured and what data is available.
Draw or describe the responsibilities needed for a Stream Processor like Flink. Trace a representative request, event or job from its input to a visible result; identify durable state owners.
Walk through a difficult case step by step, including detection and recovery. Consider: How fresh? Upgrades without losing state? Rescale later?
Compare a credible alternative using your chosen workload and guarantees. Explain a remaining risk, a signal to watch and when you would change the design.