ringpop-go

Scalable, fault-tolerant application-layer sharding for Go applications

Explore on GitHub Read Hacker News discussions

4Distinct people

4Mentions

0Explicit recommenders

882GitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

Scalable, fault-tolerant application-layer sharding for Go applications

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, 3:56:07 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 year4 dated mentions

Observed mentions: 2015-10-22 01:08:29 UTC to 2022-01-03 03:05:38 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

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Comments
2015	2015-01-01 00:00:00 UTC	2016-01-01 00:00:00 UTC	1	1
2016	2016-01-01 00:00:00 UTC	2017-01-01 00:00:00 UTC	0	0
2017	2017-01-01 00:00:00 UTC	2018-01-01 00:00:00 UTC	0	0
2018	2018-01-01 00:00:00 UTC	2019-01-01 00:00:00 UTC	1	1
2019	2019-01-01 00:00:00 UTC	2020-01-01 00:00:00 UTC	1	1
2020	2020-01-01 00:00:00 UTC	2021-01-01 00:00:00 UTC	0	0
2021	2021-01-01 00:00:00 UTC	2022-01-01 00:00:00 UTC	0	0
2022	2022-01-01 00:00:00 UTC	2023-01-01 00:00:00 UTC	1	1

What Hacker News says

4 sources

jzelinskie·Jan 3, 2022

Slicer is mentioned briefly in the PWL talk on Zanzibar[0]. I've chatted with a few folks from Uber that worked on Ringpop[1], which was inspired by Slicer, but doesn't have any of the novel dynamic balancing properties. I still don't think there's anything anbalagous outside of Google. [0]: https://youtu.be/1nbSbe3kw2U?t=1612 [1]: https://github.com/uber/ringpop-go

In Slicer: Auto-Sharding for Datacenter Applications

sytse·May 4, 2019

Yes, Ringpop was reference number 8 in the article. It is interesting that https://github.com/uber/ringpop-go says: "This project is no longer under active development" So the time of Redis has passed but the successor has passed away as well?

In Remote, in-memory key-value stores: An idea whose time has come and gone? [pdf]

freeman478·May 29, 2018

Thanks, looks quite useful. However it seems based on https://github.com/uber/ringpop-go which is marked as no longer active... What are you using to implement rate limiting ?

In Show HN: Golimit – Ringpop-based distributed and decentralized rate limiter

malandrew·Oct 22, 2015

IDLs are awesomely useful and you can build all sorts of things on that abstraction, especially if you have a parser that produces a standard AST (I wrote a PegJS parser that takes the Thrift IDLs and creates a plain old javascript object AST that can be used for things like: (1) writing dynamic serializers/deserializers for binary data (uber/thriftrw), (2) validators (not yet written, but will both lint as well as check for backwards compatibility when IDLs are updated); (3) bash autocompletion for an RPC api via a curl-like command (soon to land in uber/tcurl)) At Uber, we started with Apache Thrift, but found many things about it limited and broken with dubious code quality for some languages. Furthermore we had more ambitious ideas like application layer sharding (uber/ringpop) and service discovery and routing (uber/hyperbahn). We're

Read the rest

still using the thrift protocols (uber/thriftrw) with our rpc library (uber/tchannel), but could have built on top of another IDL format like protobufs (v3). For those curious about the RPC interface, just check out: https://tchannel.readthedocs.org/en/latest/ The interface supports all sorts of things This is all over TCP right now and designed for performance and service to service communication, but there is nothing preventing the addition of HTTP (via XHR or WebSockets) as a transport for allowing web apps to speak with tchannel services. I contributed to the Apache Thrift implementation that allows this (https://github.com/apache/thrift/blob/master/lib/nodejs/lib/...). The implementation for tchannel would be similar, but rely on XHR/WS in the browser and the `http` module instead of the `net` module in NodeJS on the server. It's trivial to write a proxy frontend that relays TJSONProtocol on the frontend to a Thrift binary protocol like TBinaryProtocol or TCompactProtocol. https://github.com/uber/hyperbahn https://github.com/uber/tchannel https://github.com/uber/ringpop-node https://github.com/uber/ringpop-go https://github.com/uber/idl https://github.com/uber/tcurl https://github.com/uber/tcap etc.

In Show HN: WebRPC – a simple alternative to REST and SOAP