Developers are living in exciting, but more demanding times - we're expected to create applications and services that can deliver better value faster, at higher volumes, with less downtime. And in order to meet these demands we must learn new technologies and programming styles. Enter the actor model and Akka.NET. In this talk you'll learn the fundamentals of Akka.NET and discover how you can use the power of the actor model, location transparency, clustering, and other Akka.NET concepts to build powerful, highly available systems without having to write awful boilerplate code. You'll never look at .NET the same way again afterwards.

1. Akka.NET
The Future of Distributed
Programming in .NET
Aaron Stannard,
Co-founder Akka.NET
@Aaronontheweb #ndcsydney

2. High Expectations for Backend
Developers

3. And the obvious ways to scale
are wrong.

4. Enterprise CRUD App

5. Scenario 1: Surge in User
Activity

6. Obvious Solution: Sharding

7. Brittle

8. Scenario 2: Real-time User
Interactivity

9. Obvious Solution: Read-after-
Write

10. Reality

11. Why is Distributed Programming
Hard?

12. Distributed Systems 101

13. Enter the Actor Model

14. Origins

15. Actor Model Core Concepts

16. Actor Model for .NET

17. Akka.NET Modules
• Akka – core actor library
• Akka.Remote – cross-node actor deployment /
communication
• Akka.Cluster – elastic actor networks (HA)
• Akka.Persistence – event-sourcing, durable actor state &
recovery
• Akka.Streams – streaming workflows
• Akka.Cluster.Tools – cluster singleton, distributed pub
sub
• Akka.Cluster.Sharding – durable state partitioning
• Akka.DData – eventually consistent data replication

18. What's an Actor?

19. Statefulness & Concurrency
with Actors

20. Actors have internal state

21. Actor state is always private,
modified when handling
messages, only shared via
immutable messages

22. Actors live in a family tree

23. Actors process one message at
a time

24. Actors share threads!

25. Actors share threads!

26. Actors on the Network

27. Properties of Messages

28. Messaging Patterns

29. Messaging Protocols

30. Communicate with Actors via
Reference

31. Actor References Have
Transparent Locations

32. Akka.Remote & Akka.Cluster:
Location Doesn't Matter

33. Fastest Response Time?

34. Stateful Apps Serve Results
from Memory

35. State Locality

36. State Makes Protocols Work

37. CAP Theorem

38. CAP Terminologies

39. CAP & Protocols

40. Fault and Resource Isolation
with Actors

41. Actor Lifecycle Phases

42. "Just let it crash"

43. DeathWatch: Subscribe to
Actors' Lifecycle

44. Petabridge