Tuesday 6th May, 2014
8:30am to 12:00pm
Architecture hoisting is a design technique for achieving a non-local property. When developers want a system to achieve a non-local property like security, performance, or scalability, they can accomplish this either through vigilant coding throughout the program or by architectural hoisting. When they hoist a property, they hand the responsibility for achieving it to the architecture, reducing or eliminating the need for developer vigilance. Sometimes a property can be hoisted by following an architectural style, but more often there will be code devoted to the architecture and specifically to achieving that property, as is seen in examples such as application servers, garbage collectors, and map-reduce frameworks.
Sign in to add slides, notes or videos to this session