This document discusses reactive systems as the future of software architecture. It notes common issues like synchronous calls and blocking I/O that reactive systems aim to address. It recommends embracing asynchronous, isolated, loosely coupled systems using reactive principles and technologies like Reactive Streams, Akka, and Play Framework to build performant, available, responsive, resilient and elastic applications. The document advocates functional programming styles, lazy evaluation, decomposing applications, denormalizing data and moving computation to data sources.

1. REACTIVE SYSTEMS
future of software architecture
Wojciech Kamiński

3. 25 mln EUR $ of public money at work
2016-02-15 18:21:20

6. TYPICAL DISEASES
➔ Synchronous method calls
➔ Blocking on IO
➔ Heavy server side state
➔ Monolithic apps

7. HOW SHOULD I BUILD MY APP
FOR 1M USERS?

8. WHAT MATTERS
➔ PERFORMANCE
➔ AVAILABILITY
➔ RESPONSIVENESS
➔ RESILIENCE
➔ ELASTICITY (aka. SCALABILITY)

9. REACTIVE MANIFESTO
http://www.reactivemanifesto.org/

10. MESSAGE DRIVEN
➔ Asynchronous
➔ Isolated
➔ Location Transparent
➔ Loosely Coupled
➔ Errors as messages

11. WHAT TO LOOK INTO
Reactive Streams
Scala
Akka
Play Framework
Apache Spark
Lagom
RxJava, RxJS,
Rx.NET, RxScala,
RxClojure, RxCpp,
Rx.rb, RxPY, RxSwift….
Akka Streams
Java 9
Spring 5

12. BEST PRACTICES

13. EMBRACE FUNCTIONAL STYLE

14. USE LAZILY EVALUATED
DATA ABSTRACTIONS

15. BREAK YOUR APP
INTO PIECES

16. BASE not ACID

17. DENORMALIZE DATA

18. TAKE THE COMPUTATION
TO YOUR (BIG) DATA

19. THANK YOU!
Wojciech Kamiński