SASandmanDZ·Nov 20, 2023Submission
Show HN: A Geo-Distributed KV Store for Metadata Management
4 points · Open discussionxline-kv
Xline
Rust2023–2023
xline-kv / Xline
Xline
A geo-distributed KV store for metadata management
5Distinct people
8Mentions
0Explicit recommenders
717GitHub stars
What to know before exploring
What it is
A geo-distributed KV store for metadata management
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by month8 dated mentions
Observed mentions: 2023-01-02 14:49:36 UTC to 2023-11-20 18:15:01 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Jan 2023 | 2023-01-01 00:00:00 UTC | 2023-02-01 00:00:00 UTC | 1 | 1 | 0 |
| Feb 2023 | 2023-02-01 00:00:00 UTC | 2023-03-01 00:00:00 UTC | 0 | 0 | 0 |
| Mar 2023 | 2023-03-01 00:00:00 UTC | 2023-04-01 00:00:00 UTC | 2 | 1 | 1 |
| Apr 2023 | 2023-04-01 00:00:00 UTC | 2023-05-01 00:00:00 UTC | 0 | 0 | 0 |
| May 2023 | 2023-05-01 00:00:00 UTC | 2023-06-01 00:00:00 UTC | 1 | 1 | 0 |
| Jun 2023 | 2023-06-01 00:00:00 UTC | 2023-07-01 00:00:00 UTC | 0 | 0 | 0 |
| Jul 2023 | 2023-07-01 00:00:00 UTC | 2023-08-01 00:00:00 UTC | 0 | 0 | 0 |
| Aug 2023 | 2023-08-01 00:00:00 UTC | 2023-09-01 00:00:00 UTC | 1 | 1 | 0 |
| Sep 2023 | 2023-09-01 00:00:00 UTC | 2023-10-01 00:00:00 UTC | 0 | 0 | 0 |
| Oct 2023 | 2023-10-01 00:00:00 UTC | 2023-11-01 00:00:00 UTC | 2 | 0 | 2 |
| Nov 2023 | 2023-11-01 00:00:00 UTC | 2023-12-01 00:00:00 UTC | 1 | 1 | 0 |
What Hacker News says
8 sourcesThe CURP paper doesn't define a new leader election algorithm and assumes you use an existing one like raft¹. Xline is using raft based on the readme
https://github.com/xline-kv/Xline/tree/master/curp/tla%2B
¹warning, I skimmed and ctrl-fd for "leader election"
In Introduction to CURP ProtocolNice to have the TLA+ spec in the repo. Though it doesn't have the details on leader election.
https://github.com/xline-kv/Xline/blob/master/curp/tla%2B/cu...
In Introduction to CURP ProtocolShow HN: Geo-Distributed Metadata Management System
1 points · Open discussionShow HN: Xline0.4.0: Geo-Distributed KV Store for Metadata Management
5 points · Open discussionShow HN: Xline v0.3.0: A Geo-Distributed KV Store for Metadata Management
3 points · Open discussionSounds interesting:
> Although Raft is stable and easy to implement, it takes 2 RTTs to complete a consensus request from the view of a client. One RTT takes place between the client and the leader server, and the leader server takes another RTT to broadcast the message to the follower servers. In a geo-distributed environment, an RTT is quite long, varying from tens of milliseconds to hundreds of milliseconds, so 2 RTTs are too long in such cases.
> We adopt a new consensus protocol named CURP to resolve the above issue. Please refer to the paper for a detailed description. The main benefit of the protocol is reducing 1 RTT when contention is not too high. As far as we know, Xline is the first product to use CURP.
It is open source, Apache license, Rust: https://github.com/datenlord/xlinehttps://github.com/datenlo...
In Show HN: A New Geo-Distributed KV Store for Metadata ManagementXline: A geo-distributed KV store for metadata management
1 points · Open discussion