The Reactive Manifesto: Message-driven, Resilient, Elastic, Responsive by Stefano Baghino presented in Milan during MTS Codemotion Tech Meetup.

1. The Reactive
Manifesto
Message driven, Fault tolerant, Elastic, Responsive

2. Hello!
I am Stefano Baghino
Software Engineer @ DATABIZ
Regular Attendee @ MTS
I code.
Therefore, I introduce bugs.

3. 0.
Reactive what?
What are we going to talk about?

4. Reactive Programming

5. Reactive Programming
Functional Reactive Programming

6. Reactive Programming
Functional Reactive Programming
Reactive Systems

7. 1.
Responsiveness
Never too late!

9. What does it mean “to be responsive”?

10. Responsive

11. Responsive
Performance

12. Boom! Nailed it!
End of story.
Right?

13. Let’s take a little step back

14. We live in a new world
Billions of users are on the Internet at any time
IoT will push the challenge up a notch
The world runs faster than your server

15. Responsive
Scalable

16. Being scalable is not enough

17. Responsive
Elastic

18. Even elasticity is not enough

19. Responsive
Elastic
Fault tolerant

20. 2.
Solid foundations
How do we get there?

21. Decouple all the things!
Decoupling is the key
Loosely coupled components scale well
Loosely coupled components can be more resilient

22. Responsive
Elastic
Fault tolerant

23. Decouple all the things!
We need a way to decouple our components
Asynchronous message passing is ideal
If naturally fits distributed systems

24. Message driven can also mean event driven
Forwarding
Request / Response
Message broker

25. Responsive
Message driven
Elastic
Fault tolerant

26. Good, how can we do it?

27. A couple of words on the Actor Model
A model for concurrent computation
Actors can only react to asynchronous messages
When a message arrives, they can only:
1. send a message
2. create a new actor
3. change their own behaviour

28. Actors: great for fault tolerance

29. Interested? Codemotion got you covered!

30. The four traits of Reactive Systems
1. Responsive
→
React to clients
2. Elastic
→
React to load
3. Fault tolerant
→
React to failure
4. Message driven
→
React to stimuli

31. What is the Reactive Manifesto?
The Reactive Manifesto is an initiative to define a tech
agnostic shared vocabulary, to define an architectural
pattern for Reactive Systems.
It’s not about dogmas, it’s about critical thinking.

32. What is the Reactive Manifesto?
Go home, read it.
If you agree, you can sign it.
If you don’t, debate. It’s only good.
If you think you can improve it, make a PR.
www.reactivemanifesto.org

33. Thanks!
Debate time? Or is it pizza?
Hey! I’ll be a speaker at Codemotion too!
Interested in Big Data? I’ll talk about Apache Spark!
You can find me at:
@stefanobaghino
stefano.baghino@databiz.it