Re:Heroku's Ugly Secret: The story of how the cloud-king tur...
by willvarfar on Thursday February 14, 2013 @02:51AM
(#5218328)
hint just use a rabbitmq queue or something. Don't have a 'smart' LB that has to know everyone's state; instead, have dynos that get more work as quick as they can.
[ Parent
| on HN ]
Re:Heroku's Ugly Secret: The story of how the cloud-king tur...
by praptak on Thursday February 14, 2013 @03:27AM
(#5218427)
MQ might be a solution but certainly not in the "just use" class. Unless you want to introduce a bottleneck and a single point of failure, this queue has to be distributed.
Managing a distributed queue is hard, for reasons similar to ones making the original problem hard - DQs require global state in a distributed environment. There are tradeoffs involved - the synchronization cost might become a bottleneck in itself.
Pushing the problem on the distributed brokers is making a big bet on the queuing solution. Nope, definitely not in the "just use" category.
Re:Heroku's Ugly Secret: The story of how the cloud-king tur...
by willvarfar on Thursday February 14, 2013 @04:42AM
(#5218695)
yes, I know all the ins and outs.
But they will end up building a pull rather than push system in the end.