Most software architectures are shaped by powerful forces which have nothing to do with technology or application requirements. These forces include, but are not limited to - Resume Driven Development, vendor's commercial interests, or the desire to be hip and ahead of the curve. What can architectures look like when we have application requirements so strong that these forces are overcome?
In this talk we will explore what architectures emerge from applying design patterns required for high-performance, efficiency, resilience, security, usability, and other quality of services measures that when not achieved result in total project failure. Surprising architectures and development approaches can emerge when the team listen to the design pressures and code accordingly. Martin has seen a number of such projects. In this talk Martin will outline emergent designs and working practices of the teams that succeed in areas where the design pressures quickly cull that which does not deliver.