Reactive Architectures

Track abstract

Since the reactive manifesto the design of many systems has moved towards being built as Reactive Systems, which are more flexible, loosely-coupled, and scalable. This makes them easier to develop and amenable to change. They are significantly more tolerant of failure and when failure does occur they meet it with elegance rather than disaster. Reactive Systems are highly responsive, giving users effective interactive feedback. Microservices is another fashion in architectures these days and the promises they hold about isolation, high cohesion and low coupling are along the lines of Reactive Systems. Join us for a track with examples and caveats explained.