uber / ringpop-go

Scalable, fault-tolerant application-layer sharding for Go applications
http://www.uber.com
MIT License
835 stars 83 forks source link

(This project is no longer under active development.) #220

Open tjstebbing opened 6 years ago

tjstebbing commented 6 years ago

Could we please get some more info about what this means? Should people avoid looking at ringpop as it's a discontinued project that uber is moving on from, or is it because you consider it feature complete and in maintenance mode?

allyraza commented 6 years ago

I would also like to know what is the reason uber abandoned it, have you guys moved on to something else

alibo commented 6 years ago

@allyraza I think you can find the answer in this talk: https://www.youtube.com/watch?v=MDuagr729aU

CorgiMan commented 6 years ago

It is my understanding that Uber is slowly moving away from Ringpop, however, it is still being used in a lot of its critical services. There hasn't been any incidents caused directly by Ringpop after Uber stopped maintaining it I believe and I think that if any big issues will be found, they would be fixed. However, Uber doesn't need any more features from Ringpop and learned how to deal with it's shortcomings. I recently spoke to some folks who told me that Ringpop starts to break at clusters of 1600 nodes for example.

So if you are looking to use it, you sure can! There is no guarantee however that you wouldn't run in any problems because you might set it up a bit differently than Uber does.