Reactive Microsystems—The Evolution of Microservices at Scale

Title: Reactive Microsystems—The Evolution of Microservices at Scale
Date: 11/15/17
Time: 12:00 PM ET
Duration: 1 Hour

Jonas Bonér
Founder and CTO of Lightbend, Inventor of Akka project

Registration Link
Case Study Interview

Q: Can a new fact disprove an existing fact?
Viktor: Yes, a new fact can add the information that a previous fact was wrong/false.

Q: What is main benefit of Reactive design?
Viktor: The goal of Reactive design is to achieve Responsiveness—the ability to provide a response within a reasonable timeframe.
In order to provide that, the system needs to deal with failure (be resilient) and with load (be elastic)—and the way to achieve that is to build it on top of Message-Passing.

Q: How do you think state-machine under event-driven architecture?
Viktor: You can view it as a fold-operation on a logical stream of events, where the value of the fold is the state-machine, and events are applied to the state machine in order of reception to yield the next state.

Q: Please give an example of applying back pressure.
Viktor: In practice, anywhere where you want to create an upper bound on work-in-progress.
As an example, transferring events from storage to processing. Or inbound requests to a server.