Your SlideShare is downloading. ×
Reactive application
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Reactive application

225

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

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
225
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
4
Comments
0
Likes
2
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Reactive Application Christophe Marchal Rafael Souza @toff63 @rafael_psouza
  • 2. Object Oriented Programming Hard to reuse objects Functional Programming Easy to reuse small functions Functional Paradigm: Composition
  • 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. Tools for application development
  • 5. Evolution of large applications
  • 6. Response Time
  • 7. Uptime
  • 8. Data Size
  • 9. Hosting
  • 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. Reactive traits
  • 12. Scaling up
  • 13. Scaling out
  • 14. Concurrency handled by container
  • 15. More user, more thread
  • 16. Efficiency issue
  • 17. Thread dump result
  • 18. Computer time scale
  • 19. Paradigm shift: Event driven
  • 20. Scala Future
  • 21. Handling failure
  • 22. Traditional Failure Handling
  • 23. Node stop responding
  • 24. Domino effect
  • 25. Bulkhead pattern
  • 26. ● Stateful ● Asynchronous ● Only communicate through message Create Bulk: Actors
  • 27. Actor tree
  • 28. Akka: Supervision
  • 29. Akka: Supervision
  • 30. Streaming data to the screen
  • 31. Using Play! 2.3-M2
  • 32. Websocket
  • 33. Controller
  • 34. Backend Actor
  • 35. Thanks! Obrigado! Christophe Marchal Rafael Souza @toff63 @rafael_psouza

×