Reactive has become an overloaded term these days and is now being associated as several different things to different people—in good company with words like “streaming,” “lightweight,” and “real-time.” However, from the perspective of software architecture, reactive is a set of design principles, a way of thinking about systems architecture and design in a distributed environment where implementation techniques, tooling, and design patterns are components of a larger whole—a system. But what’s the barrier to entry for getting started with this type of architecture? How do we know which tools and frameworks are the best fit for our organization’s business objectives? What role does reactive architecture play in the IoT and mobile landscapes?
©2017, 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