search

customerio / fairway

A fair way to queue messages in multi-user systems.
59 stars 6 forks source link

Lessons Learned and Current Status #14

Open woodhull opened 2 weeks ago

woodhull commented 2 weeks ago

Hello!

We've got the same problem that fairway attempts to solve: A rails app, using sidekiq, that needs to fairly allocate the limited capacity of our downstream providers across multiple customer accounts.

It seems like CustomerIO may have moved on from this implementation since there has not been very much activity recently.

We were thinking about adopting this code for our product after doing some modernization work. What were the lessons learned or things we should know about? What caused y'all to move in a different direction? Is anyone else currently actively using this?

woodhull commented 1 week ago

We're going to use shuffle sharding instead.

https://aws.amazon.com/builders-library/workload-isolation-using-shuffle-sharding/ https://www.mikeperham.com/2019/12/17/workload-isolation-with-queue-sharding/