SQS) — Simple#

Problem statement (interviewer prompt)

Design Kafka (or RabbitMQ / SQS): producers publish messages to topics, consumers read in groups for parallelism. Provide partitioned ordering, configurable retention, at-least-once + exactly-once semantics, replication for HA, and tiered storage for cold data.

flowchart LR
  P[Producer]
  B[[Broker]]
  T[[(Topic / Partitions)]]
  C[Consumer Group]
  P --> B --> T --> C

    classDef client fill:#dbeafe,stroke:#1e40af,stroke-width:1px,color:#0f172a;
    classDef edge fill:#cffafe,stroke:#0e7490,stroke-width:1px,color:#0f172a;
    classDef service fill:#fef3c7,stroke:#92400e,stroke-width:1px,color:#0f172a;
    classDef datastore fill:#fee2e2,stroke:#991b1b,stroke-width:1px,color:#0f172a;
    classDef cache fill:#fed7aa,stroke:#9a3412,stroke-width:1px,color:#0f172a;
    classDef queue fill:#ede9fe,stroke:#5b21b6,stroke-width:1px,color:#0f172a;
    classDef compute fill:#d1fae5,stroke:#065f46,stroke-width:1px,color:#0f172a;
    classDef storage fill:#e5e7eb,stroke:#374151,stroke-width:1px,color:#0f172a;
    classDef external fill:#fce7f3,stroke:#9d174d,stroke-width:1px,color:#0f172a;
    classDef obs fill:#f3e8ff,stroke:#6b21a8,stroke-width:1px,color:#0f172a;
    class P,C service;
    class T datastore;
    class B queue;