A collection of examples for throttling in java. Throttling can be useful in systems with high load, like a web application, or middleware.
Throttling is any behavior that limits the total amount of work processed regardless of how much work is offered, without crashing the system. The key to throttling is to do something other than regularly processing the work. The alternative process should need much less resources. For example a web site might still render headers and footers, but render a "Sorry, too busy" message instead of user content to relieve the database.
Built in behavior in overload scenarios can protect a system from failing badly. Without throttling systems can become unpredictable, severely crippled, or totally hung. This happening on production can severely impact user experience and business. A calculated and tested scenario is typically preferred over a surprise.
For now just check out the code and look at the testcases. This is more like a set of recipes than a framework.
Meh, licenses are boring.