News for hackers. Stuff that matters.
Re:Google Doorman: Global Distributed Client Side Rate Limiting by rixed on Sunday April 10, 2016 @12:51AM (#11464952)
Rate limiting looks outdated. Suppose you can spawn new servers (and turn down unused ones) fast enough to react to demand, and have a good LB that sends the traffic where you have capacity, then you do not need to limit anything until you reach full capacity, in which case you probably want to degrade (by query class and/or client class) rather than limit anyway.

Rate limiting is an inefficient way to distribute a service, that makes sense only if you preallocate your resources and have queries with predictable cost. Let's use this technique only as a bug-prevention tool not for resource economy, as organised scarcity is likely as inefficient for the data center as it is for the distribution of goods :)

Re:Google Doorman: Global Distributed Client Side Rate Limiting by greenleafjacob on Sunday April 10, 2016 @08:11AM (#11465842)
If you degrade by client or query class then in the case of just one class of query or one class of client you would have an unfair distribution, because one client could consume many resources and others would be limited to whatever's available on the margins.

I would like to see an adaptive system that, when resources are scarce, pushes towards a more equitable distribution.