We build distributed systems to maintain high availability and improve performance. However, as soon as distributed state is thrown into the mix, you have to start thinking about the performance costs of accessing that state and keeping it current. Many of the worst problems concern the need for coordination across nodes and across systems within a node.
Drawing on the lessons he’s learned working on Wallaroo, a high-performance, open source framework for building stateful distributed applications, John Mumm shares strategies for avoiding coordination and relying on local knowledge wherever possible along with pros and cons and tips for using in-memory state instead of the typical approach of using external data stores.
John Mumm is a software architect at Wallaroo Labs based in Netherlands, where he works on an open source high-performance framework for building stateful distributed applications. John holds a PhD in philosophy.
For exhibition and sponsorship opportunities, email velocity@oreilly.com
For information on trade opportunities with O'Reilly conferences, email partners@oreilly.com
View a complete list of Velocity contacts
©2018, 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. • confreg@oreilly.com