Most Internet and Enterprise systems require N-9s availability, for N >= 5. These systems often have tight responsiveness requirements, too. Meeting such requirements isn’t a new problem, but the requirements have grown tighter and more pervasive over time. Even systems with relatively modest requirements can benefit from the techniques used in such systems.
The Reactive Manifesto was created by several leaders in the fields of distributed systems and high-performance computing to codify several core traits that are universally essential for such Reactive systems. The Manifesto has been refined since it was introduced, in response to feedback from many people.
The traits are the following:
I’ll describe how the four traits impact system architectures, without being overly prescriptive.
None of them is new, but many systems that claim to be reactive fall short in one or more of these areas.
We’ll examine several representative examples to understand how the traits are realized in practice.
Dean Wampler, Ph.D., is the Architect for Big Data Products and Services for Typesafe. He builds scalable, distributed applications using Spark, Hadoop, Mesos, Scala, and the Typesafe Reactive Platform. He is the author of several books for O’Reilly on Scala, Hive, and Functional Programming. Dean is a contributor to several open source projects and he co-organizes several technology conferences and Chicago-based user groups. Follow Dean on Twitter @deanwampler.
For exhibition and sponsorship opportunities, contact Sharon Cordesse at firstname.lastname@example.org
For information on trade opportunities with O'Reilly conferences, email email@example.com
For media-related inquiries, contact Maureen Jennings at firstname.lastname@example.org
View a complete list of Software Architecture contacts
©2015, 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