Caches, Modes, and Unstable Systems

This page summarizes the projects mentioned and recommended in the original post on news.ycombinator.com

InfluxDB - Power Real-Time Data Analytics at Scale
Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
www.influxdata.com
featured
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com
featured
  • viewstamped-replication-made-famous

    Discontinued A $20k consensus challenge based on TigerBeetle's implementation of the pioneering Viewstamped Replication protocol. [Moved to: https://github.com/tigerbeetledb/viewstamped-replication-made-famous] (by coilhq)

  • As an example of this in distributed systems:

    There's a classic metastability issue in probably most implementations of state machine replication protocols such as Raft, where a lagging follower, if it sees an op that's newer than what it's expecting, must first repair and catch up its state (FIFO) before it can ACK back to the leader.

    Apart from introducing latency in the critical path, this can lead to really bad queueing behavior where the lagging follower queues the latest request from the leader while it first catches up, but because this catch up can take seconds or minutes, in that time the pending request queue has also overflowed, and now we're back to state transfer catch up all over again, a vicious cycle.

    Raft requires this bimodal latency distribution for correctness.

    However, there is a new approach that we developed for TigerBeetle [1] to eliminate this bimodality and achieve constant ACK latencies from all followers, no matter their state, that we'll be sharing as part of Viewstamped Replication Made Famous [2], a $20,000 consensus challenge launching in September.

    [1] https://www.tigerbeetle.com

    [2] https://github.com/coilhq/viewstamped-replication-made-famou...

  • As an example of this in distributed systems:

    There's a classic metastability issue in probably most implementations of state machine replication protocols such as Raft, where a lagging follower, if it sees an op that's newer than what it's expecting, must first repair and catch up its state (FIFO) before it can ACK back to the leader.

    Apart from introducing latency in the critical path, this can lead to really bad queueing behavior where the lagging follower queues the latest request from the leader while it first catches up, but because this catch up can take seconds or minutes, in that time the pending request queue has also overflowed, and now we're back to state transfer catch up all over again, a vicious cycle.

    Raft requires this bimodal latency distribution for correctness.

    However, there is a new approach that we developed for TigerBeetle [1] to eliminate this bimodality and achieve constant ACK latencies from all followers, no matter their state, that we'll be sharing as part of Viewstamped Replication Made Famous [2], a $20,000 consensus challenge launching in September.

    [1] https://www.tigerbeetle.com

    [2] https://github.com/coilhq/viewstamped-replication-made-famou...

  • InfluxDB

    Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

    InfluxDB logo
  • tigerbeetle

    Discontinued A distributed financial accounting database designed for mission critical safety and performance. [Moved to: https://github.com/tigerbeetledb/tigerbeetle] (by coilhq)

  • As an example of this in distributed systems:

    There's a classic metastability issue in probably most implementations of state machine replication protocols such as Raft, where a lagging follower, if it sees an op that's newer than what it's expecting, must first repair and catch up its state (FIFO) before it can ACK back to the leader.

    Apart from introducing latency in the critical path, this can lead to really bad queueing behavior where the lagging follower queues the latest request from the leader while it first catches up, but because this catch up can take seconds or minutes, in that time the pending request queue has also overflowed, and now we're back to state transfer catch up all over again, a vicious cycle.

    Raft requires this bimodal latency distribution for correctness.

    However, there is a new approach that we developed for TigerBeetle [1] to eliminate this bimodality and achieve constant ACK latencies from all followers, no matter their state, that we'll be sharing as part of Viewstamped Replication Made Famous [2], a $20,000 consensus challenge launching in September.

    [1] https://www.tigerbeetle.com

    [2] https://github.com/coilhq/viewstamped-replication-made-famou...

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts

  • Zignal: An image processing library written in Zig

    1 project | news.ycombinator.com | 10 May 2024
  • Show HN: I made a better Perplexity for developers

    5 projects | news.ycombinator.com | 8 May 2024
  • Ziglang-Set: generic and general-purpose Set implementation for Zig

    1 project | news.ycombinator.com | 7 May 2024
  • Node Test Runner vs Bun Test Runner (with TypeScript and ESM)

    1 project | dev.to | 26 Apr 2024
  • SPA-Like Navigation Preserving Web Component State

    2 projects | dev.to | 25 Apr 2024