Download as PDF, PPTX
Uploaded bypetabridge
Akka.NET: Concurrency Without the Pain (Intro to the Actor Model)
The document introduces the actor model as a solution to the complexities of multithreading and concurrency in programming. It describes how actors communicate through message passing, which simplifies synchronization and enhances scalability. The content emphasizes the challenges of traditional shared state programming and illustrates the benefits of using the actor model for building robust and thread-safe applications.
More Related Content
Similar to Akka.NET: Concurrency Without the Pain (Intro to the Actor Model)
Akka.NET: Concurrency Without the Pain (Intro to the Actor Model)
- 1. @petabridge Petabridge.com Concurrency Withoutthe Pain: An Intro to the Actor Model Andrew Skotzko Co-‐founder — Petabridge
- 2.
- 3. @petabridge Petabridge.com Why should we care about concurrency?
- 4.
- 5.
- 6.
- 7.
- 8.
- 9. @petabridge Petabridge.com TANSTAAFL “There ain’t no such thing as a free lunch.” —R. A. Heinlein, The Moon Is a Harsh Mistress
- 10.
- 11. @petabridge Petabridge.com WTF are you talking about?
- 12. @petabridge Petabridge.com Concurrency. Time to make friends.
- 13. @petabridge Petabridge.com So what’s the problem?
- 14. @petabridge Petabridge.com How toWrite Multithreaded Code Shared State Programming Make classes and functions Find areas where you can do multiple things at once Queue work onto a new thread or thread pool Use synchronization mechanisms to protected shared memory (what?!?!) Finish work on one thread Consume that work on another
- 15. @petabridge Petabridge.com Shared StateProgramming Sucks (Illustrated) Shared State Programming Problems Synchronizing shared state == pit of doom Deadlocks Livelocks Unsafe state Coordinating work between threads Debugging multi-threaded code: not for the faint of heart Hey, that third party code you're using - is it thread safe? Writing thread-safe code is hard
- 16. @petabridge Petabridge.com Random? • .NET4.0: TPL (2010) • .NET 4.5: async/await (2012)
- 17. @petabridge Petabridge.com Is therea better way? THERE MUST BE! THERE. MUST. BE. A. BETTER. WAY!
- 18. @petabridge Petabridge.com Warning! Mind BlowinglyDifferent Programming Style Ahead!
- 19. @petabridge Petabridge.com Warning! MindBlowingly Different Programming Style Ahead!
- 20.
- 21. @petabridge Petabridge.com What is the actor model?
- 22. @petabridge Petabridge.com Everything is an actor.
- 23.
- 24.
- 25. @petabridge Petabridge.com 3 CoreAbilities 1. Send messages 2. Create other actors 3. Change behavior
- 26.
- 27. @petabridge Petabridge.com Actors workby passing each other messages
- 28. @petabridge Petabridge.com Message passingin action Send "Hello" to "/user/actor1" Received "Hello" from "/user/actor2" (do some work) Send "Sup homedawg" to "/user/actor2"
- 29.
- 30.
- 31. @petabridge Petabridge.com Actors sendmessages to addresses akka.tcp://MySystem@localhost:9001/user/actorName1 Protocol ActorSystem Address Path All parts form an "ActorPath"
- 32. @petabridge Petabridge.com Actor addresseshave location transparency
- 33.
- 34.
- 35.
- 36. @petabridge Petabridge.com Magical scalingsauce! (more on that later)
- 37.
- 38. @petabridge Petabridge.com What isAkka.NET?
- 39. @petabridge Petabridge.com Obligatory logosto impress you
- 40.
- 41.
- 42. @petabridge Petabridge.com Actors runon threads
- 43.
- 44. @petabridge Petabridge.com Process messagesone at a time
- 45.
- 46.
- 47.
- 48.
- 49.
- 50.
- 51.
- 52.
- 53.
- 54. @petabridge Petabridge.com We CanDeploy Actors and Send Messages Anywhere Nice hair! Did you hear? My hair rocks! Dude, don't encourage him.
- 55. @petabridge Petabridge.com Scaling Out •Actors can be deployed anywhere • Special "Router" actors distribute work • Actors can be easily restarted and redeployed
- 56. @petabridge Petabridge.com And CanForm Highly Available Systems Ready for work!
- 57.
- 58. @petabridge Petabridge.com Have questions?Ask us! andrew@petabridge.com Intro: http://learnakka.net
- 59.
- 60.