Database Architect

vilmate, Київ, Варшава (Польща)

Що робити

Diagnose the PostgreSQL failure. Before proposing anything, determine what specifically broke: write amplification, index bloat, vacuum pressure, connection saturation, fanout query cost, or storage layout. A proposal that does not explain why Postgres failed is not a proposal.
Design the hot/cold split. 500 TB cannot be uniformly hot. Define what stays on NVMe, what moves to bulk disk, what moves to object storage, and the mechanism that moves it.
Design ingestion and backfill. Firehose consumption, ordering guarantees, replay/backfill after outage, and idempotency. Kafka or equivalent as a buffer.
Design for the sharding boundary. Multi-tenant across federated networks. Define the shard key and its consequences.
Deliver a benchmarked PoC. Two candidate architectures, real firehose data, real query shapes, published numbers.

Firehose ingestion — continuous, append-heavy write stream of commits (posts, likes, follows, reposts, blocks) from relays. Sustained high write throughput, no natural backpressure.
Social graph — follows/blocks/mutes. Read-hot, latency-critical, traversal-heavy. Fanout for timeline construction.
Timeline / feed serving — low-latency reads under high concurrency. Fanout-on-read vs. fanout-on-write is an open decision.
Aggregations & counters — like counts, reply counts, repost counts. High-cardinality, high-churn, read-hot.
Search & discovery — full-text over posts, plus trend detection.

Знайдено через trackr.help/jobs · Канал: @trackrhelp · Бот для персональних сповіщень: @trackrhelpBot