INTERACTIVE SYSTEM DESIGN

Соберите систему. Защитите решения.

Меняйте вводные, собирайте компоненты и проверяйте не «правильную картинку», а явные failure domains, capacity и trade-offs.

CASE / OLTP / burst traffic / user-facing reads

Marketplace order status

Design the status path for a marketplace launch. Writes must not disappear, repeated commands are possible, and read traffic spikes after every campaign notification.

A committed status transition and its integration event must not diverge.
A client can repeat the same command after an ambiguous timeout.
Campaign reads may be stale for seconds, but writes may not reorder.

Traffic12000 RPSReads88%Availability99.95%Retries2%Retention30 days

01 / COMPONENTS

Состав системы

Consistency

Retry identity

Delivery

Cache

02 / TOPOLOGY

Рабочая схема

INJECTED / PostgreSQL primary unavailableBLAST RADIUS PROPAGATES

The order database stops serving writes during a campaign burst. Without a replica-backed source of truth, the write path has no named recovery target and the order API remains unavailable.

Selected pathInjected failure / pressureContainment boundary

READ10560/s

WRITE1440/s

NETWORK134 Mb/s

RAW / DAY1452 GB

PARTITIONS1

RETENTION43.5 TB

RETRIES240/s

03 / DESIGN REVIEW

Проверка решений

Проверка учитывает выбранный сценарий и текущие значения нагрузки. Изменение вводных сбрасывает прошлую оценку.