Juno Design Summit has ended
Back To Schedule
Tuesday, May 13 • 5:30pm - 6:10pm
Scaling an Individual Queue

Sign up or log in to save this to your schedule, view media, leave feedback and see who's attending!

I'd like to discuss different scaling strategies and brainstorm around ways we can implement them. Based on the discussion, we can create a blueprint to document the path forward.

--1-- Scale-up by adding the ability to migrate a queue to a higher-performance or lower-densisty storage partition. How would we do this with zero downtime for the user? Should this be manual, automatic, or both? If automatic, should we migrate to consistent hashing for placement?
--2-- Scale-out by adding the ability to shard a single queue across multiple backend storage partitions. The tick with this is continuing to guarantee once-and-only-once delivery in light of the fact that getting things out of order can lead to missing a message when using the feed/listing interface.

(Session proposed by Kurt Griffiths)

Tuesday May 13, 2014 5:30pm - 6:10pm EDT

Attendees (0)