ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Learn how to select the right Kafka producer 'acks' setting to balance throughput and durability, and why 'acks=all' requires 'min.insync.replicas' to be effective.
Learn how to use the Vert.x Event Bus send() method to distribute workloads across multiple verticles using point-to-point messaging and avoid common event-loop blocking pitfalls.
Explore how Twitter's fan-out architecture optimizes read latency by shifting the computational burden from the reader to the writer, and how a hybrid model handles the 'celebrity' scale problem.
Learn how gRPC deadlines propagate a time budget across service calls, stop zombie requests, and prevent resource exhaustion in distributed systems.
Learn how to use Redis Pub/Sub for real-time signaling. Understand the fire-and-forget mechanism, the subscriber state, and why it differs from message queues.
Learn how to choose between transient, durable, and quorum queues in RabbitMQ to balance data safety against system throughput and I/O performance.
Gossip Propagation and Sequencing Waku employs a decentralized gossip-based protocol to propagate messages across a peer-to-peer network. While the store-and-forward mechanism ensures that offline peers can eventually retrieve missed data, the protocol does not natively guarantee a global deterministic order for message arrival across varying network topolog
The National Public Safety System (NPSS) utilizes idempotent request keys at the API gateway layer to prevent duplicate state changes during request retries. This mechanism is designed to ensure that retransmitted packets do not result in multiple writes to the policy enforcement points (PEPs). A challenge arises when multiple administrative nodes attempt to
Schema-on-Read Versioning LinkedIn's Espresso database uses a schema-on-read approach for versioned attributes to maintain backward compatibility during multi-phase rollouts. By decoupling schema changes from data migration, older application versions can coexist with newer data formats, typically because new fields are optional or carry defaults that previo
apachekafka
vertx
redis
grpc
waku
npss
linkedin