hardScenarioDesign
A Kafka-style consumer down for an hour has missed an offset range, not necessarily lost data. If retention still covers the gap, it resumes from the committed offset; catch-up needs surplus throughput, idempotent handlers, event-time logic and a plan for retention expiry. Use this event driven answer to show the decision, trade-off, and evidence rather than a memorised definition.
hardScenarioDesign
A job queue backlog should be classified into expired jobs, superseded jobs and still-required jobs. Drain the last fully; shed expired work with a record and collapse superseded work by key. Deadlines and collapse keys must be written at enqueue time. It also connects backpressure to the point an interviewer is testing.
hardScenarioDesign
An analysis of the architectural reality of exactly-once guarantees in Flink, from distributed snapshots to two-phase commits. Use this data engineering answer to show the decision, trade-off, and evidence rather than a memorised definition. It also connects streaming to the point an interviewer is testing.
hardDesignCase Study
The server holds one row per message, partitioned by conversation and clustered by descending sequence so a page is a contiguous read, and clients page by keyset cursor rather than offset. Per-user state moves to a side table so the body stays shared, and if messages are end-to-end encrypted the wipe is a key-custody question, not a storage one.
hardScenarioDesign
An architectural examination of Dead Letter Queues, atomic offset management, and schema enforcement in high-throughput Kafka consumers. Use this distributed systems answer to show the decision, trade-off, and evidence rather than a memorised definition. It also connects KAFKA to the point an interviewer is testing.
hardDesignConcept
A queue distributes work and forgets each message once acknowledged; a log is a retained, partitioned, replayable record that many consumers read independently at their own offsets. Use this message queues answer to show the decision, trade-off, and evidence rather than a memorised definition. It also connects event log to the point an interviewer is testing.
hardScenarioDesign
Every producer must have a declared answer — block, buffer to a bounded local store, or drop — chosen per event class rather than once for the whole fleet, because the default of blocking on a full in-memory buffer turns a broker outage into an outage of every service that publishes to it.
hardDesignScenario
Chat ordering with offline clients separates ephemeral typing indicators from durable messages. Messages need a server-assigned per-conversation sequence and a client-generated id for deduplication, so reconnecting phones replay outboxes without duplicates.