Reactive Application
Christophe Marchal Rafael Souza
@toff63 @rafael_psouza
Object Oriented Programming
Hard to reuse objects
Functional Programming
Easy to reuse small functions
Functional Paradigm...
“In modern applications involving highly
concurrent computing on multicore machines,
state is the problem”
Functional prog...
Tools for application development
Evolution of large applications
Response Time
Uptime
Data Size
Hosting
“reacting to events or situations rather than
acting first to change or prevent something”
Cambridge
“Showing a response t...
Reactive traits
Scaling up
Scaling out
Concurrency handled by container
More user, more thread
Efficiency issue
Thread dump result
Computer time scale
Paradigm shift: Event driven
Scala Future
Handling failure
Traditional Failure Handling
Node stop responding
Domino effect
Bulkhead pattern
● Stateful
● Asynchronous
● Only communicate through message
Create Bulk: Actors
Actor tree
Akka: Supervision
Akka: Supervision
Streaming data to the screen
Using Play! 2.3-M2
Websocket
Controller
Backend Actor
Thanks!
Obrigado!
Christophe Marchal Rafael Souza
@toff63 @rafael_psouza
Reactive application
Reactive application
Reactive application
Upcoming SlideShare
Loading in …5
×

Reactive application

515 views

Published on

Talk about Functional application and Reactive application with example of Scala Future, Akka actors and a chat using the latest play framework version

Published in: Technology
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
515
On SlideShare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
6
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Reactive application

  1. 1. Reactive Application Christophe Marchal Rafael Souza @toff63 @rafael_psouza
  2. 2. Object Oriented Programming Hard to reuse objects Functional Programming Easy to reuse small functions Functional Paradigm: Composition
  3. 3. “In modern applications involving highly concurrent computing on multicore machines, state is the problem” Functional programming: A step backward - infoworld.com Functional Paradigm: Stateless
  4. 4. Tools for application development
  5. 5. Evolution of large applications
  6. 6. Response Time
  7. 7. Uptime
  8. 8. Data Size
  9. 9. Hosting
  10. 10. “reacting to events or situations rather than acting first to change or prevent something” Cambridge “Showing a response to a stimulus” Oxford What Reactive means?
  11. 11. Reactive traits
  12. 12. Scaling up
  13. 13. Scaling out
  14. 14. Concurrency handled by container
  15. 15. More user, more thread
  16. 16. Efficiency issue
  17. 17. Thread dump result
  18. 18. Computer time scale
  19. 19. Paradigm shift: Event driven
  20. 20. Scala Future
  21. 21. Handling failure
  22. 22. Traditional Failure Handling
  23. 23. Node stop responding
  24. 24. Domino effect
  25. 25. Bulkhead pattern
  26. 26. ● Stateful ● Asynchronous ● Only communicate through message Create Bulk: Actors
  27. 27. Actor tree
  28. 28. Akka: Supervision
  29. 29. Akka: Supervision
  30. 30. Streaming data to the screen
  31. 31. Using Play! 2.3-M2
  32. 32. Websocket
  33. 33. Controller
  34. 34. Backend Actor
  35. 35. Thanks! Obrigado! Christophe Marchal Rafael Souza @toff63 @rafael_psouza

×