The document discusses the transition toward reactive architecture in software systems, highlighting the challenges of scaling traditional applications. It emphasizes the importance of resilience, elasticity, and message-driven processes to maintain responsiveness and efficiency. The author advocates for microservices and actor-based frameworks as effective implementations for achieving these goals.

1. Reactive Architecture

2. Reactive Architecture
What’s it all about?

3. 2005
Hyundai Elantra looks like this…
Internet has 1 billion users
Facebook has 5.5 million users
Twitter doesn’t exist yet
MySpace is acquired for $850,000,000
Youtube is launched

4. 2016
Hyundai Elantra looks like this…
Internet has 3.5 billion users
Facebook has 1.5 billion users
Twitter has 0.31 billion users
Youtube has 1.3 billion users

5. A SINGLE website may now handle as much
traffic as the ENTIRE (!) Internet did a decade
ago…

6. We need to change the
Paradigm!

7. Vehicle Fleet Tracker
Application Breakdown

8. Requirements
Track GPS Locations
Assign transits
Optimise routes
Monitor vehicle stats
Calculate costs

9. The Killer Feature:
Suggest speed and direction for:
Optimised fuel consumption
Optimised arrival speed
Optimise speed for ‘catching’ green lights

10. Presentation
Business Logic
Data Access
DB
Model
Multilayered Architecture (Old School)
Driver
Dispatcher

11. –Everett Dirksen
“A billion here, a billion there, and pretty soon
you're talking about real money…”

12. We need to Scale up!
To make $$$

13. Alas, heavy loads pose
heavy issues…

14. We Need to:
1. Keep the system Responsive - especially at peaks
2. Make sure the system doesn’t crash and is Resilient
3. Avoid extreme costs during downtime - Flexible

15. Responsive
Rapid and consistent response times
Achieved through:
Resilience
Scalability (Flexibility)
A Message-Driven foundation

16. Asynchronous
Processing
The key is:

17. The Synchronous
Approach
Cut Salad - 5 min
Make Toast - 3 min
Boil eggs - 10 min
Eat
…Took 18 minutes

18. The Asynchronous
Approach
Boil Eggs - 10 min
Cut salad - 5 min
Make Toast - 3 min
Eat
…Took 10 minutes

21. We Achieve System-Wide Async via
Message Driven
Architecture

22. Message-Driven
Process
A
Process
B
Process
C

23. Message Driven
Vs.
Event Driven
Messages have a specific recipient
Events can have multiple handlers

24. Reactive Architecture
Enter:

26. Responsive
Message Driven
ResilientElastic/Scalable
Reactive Manifesto

27. Message-driven
Resiliency
Isolation
Location Transparency
Separate error channel

28. Message-driven
Scalability
Scale out on demand
No shared mutable state
No hardware limitation

29. Implementation using
Micro-Services

30. Micro Services
Message/Event driven
Resilient
Isolated and self contained
Clustered
Distributed
Elastic/Scalable

31. Implementation using
Actor Based Framework -
AKA AKKA

32. What’s an Actor
An actor is a construct with the following
properties:
- A mailbox for receiving messages
- The actor’s logic
- Isolated state

35. Summary
Traditional Monolithic applications with thread
based concurrency are:
Difficult to scale out
Not resilient
Prone to fail under stress
Reactive Architecture is a viable solution

36. Summary 2
The formula for Reactive Architecture is:
(Resilience + Elasticity) x Message-Driven = Responsive

37. Thank You
Assaf Gannon
assaf@tikalk.com