Engineering the Future of Software
April 2–3, 2017: Training
April 3–5, 2017: Tutorials & Conference
New York, NY

Reactive and its variants

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?

Add to your personal schedule
9:00am–12:30pm Monday, April 3, 2017
Location: Beekman Parlor
Level: Intermediate
Konrad Malawski (Lightbend), Henrik Engstrom (Lightbend)
Akka, the distributed systems toolkit, has been pushing the envelope of distributed and reactive systems for many years now. Konrad Malawski and Henrik Engström walk you through writing services using state-of-the-art technology like Akka Cluster and Streams and expose them as microservices using Akka HTTP, Play, or Lagom. Read more.
Add to your personal schedule
2:15pm–3:05pm Wednesday, April 5, 2017
Location: Sutton South/Regent Parlor
Level: Intermediate
Jeffrey Smith (x.ai)
Machine-learning systems can be designed to be just as reactive as the most bulletproof web or mobile app. It takes a system-level understanding of your machine-learning system and a team-level commitment to continual evolution. But you can succeed. Jeffrey Smith shows you how. Read more.