A lot of architectures we see are driven by powerful forces that have nothing to do with technology or application requirements. These forces include but are not limited to résumé-driven development, vendors’ commercial interests, and the desire to be hip and ahead of the curve. What do architectures look like when we have application requirements so strong that these other forces are overcome?
Martin Thompson explores the architectures that emerge from applying design patterns required for high performance, resilience, security, usability, and other quality-of-services measures that when not achieved result in total project failure. Martin outlines emergent designs and working practices that succeed in these areas where the design pressures quickly cull that which does not deliver.
Martin Thompson is a Java Champion with over two decades of experience building complex and high-performance computing systems. He is most recently known for his work on Aeron and SBE. Previously, he was the cofounder and CTO at LMAX, where he created the Disruptor. Prior to LMAX, Martin worked for Betfair and three different content companies wrestling with the world largest product catalogues and was a lead on some of the most significant C++ and Java systems of the 1990s in the automotive and finance domains. Martin blogs at Mechanical Sympathy and can be found giving training courses on performance and concurrency when he is not cutting code to make systems better.
Comments on this page are now closed.
©2016, O'Reilly Media, Inc. • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • email@example.com