The Reactive Manifesto

The Reactive Manifesto

Message driven, Fault tolerant, Elastic, Responsive

9bdb9cc374e313876de99a99d191ecd6?s=128

Stefano Baghino

October 27, 2015
Tweet

Transcript

  1. 2.

    Hello! I am Stefano Baghino Software Engineer @ DATABIZ Regular

    Attendee @ MTS I code. Therefore, I introduce bugs.
  2. 8.
  3. 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
  4. 21.

    Decouple all the things!   Decoupling is the key  

    Loosely coupled components scale well   Loosely coupled components can be more resilient
  5. 23.

    Decouple all the things!   We need a way to

    decouple our components   Asynchronous message passing is ideal   If naturally fits distributed systems
  6. 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
  7. 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
  8. 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.
  9. 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
  10. 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