The document discusses building applications with Akka.NET, emphasizing the importance of concurrency and the reactive systems architecture that includes responsive, resilient, and scalable components. It outlines the actor model, which facilitates message-driven communication and error isolation, while also providing examples and steps to implement actors in Akka.NET. Additionally, it mentions practical applications in the Internet of Things and the role of libraries in managing scalability and error handling.

1. BUILDING
APPLICATIONS
WITH AKKA.NET
ANTHONY BROWN
@BRUINBROWN93

2. Hi, i’m Anthony
university student
me@anthonyjbrown.co.uk
@bruinbrown93

3. moore’s law

4. now we need
concurrency…

5. …but concurrency is hard

6. MULTITHREADING
THEORY
PRACTICE

7. CHECK OUT
MY MULTITHREADED CODE

8. HOW MANY THREADS
DOES IT TAKE TO CHANGE A LIGHTBULB?

9. application requirements
have changed

10. Credit: http://www.theawl.com/wp-content/uploads/2010/08/Screen-shot-2010-08-17-at-2.11.10-PM.png

11. Common language to define
new style of architecture

12. Reactive
systems

13. RESPONSIVE
RESILIENT ELASTIC
MESSAGE PASSING

15. responsive
users want the best possible experience

16. reactive applications react
to the world around them

17. Message driven
architecture
decouples components

18. the actor
model

19. concurrency
model

20. STORAGE
isolate mutable state

21. processing
reacting to changes

22. Communication
messaging as a requirement

23. an actor is
A mailbox behaviour state

24. an actor can…
set it’s behaviour
for the next message

25. an actor can…
send a finite number
of messages

26. an actor can…
spawn a finite
number of actors

27. looking at the
original

28. erlang
99.9999999% uptime

29. erlang example

30. introducing the
akka.net way

32. step 1
define an actor

33. class
GreetingActor
:
ReceiveActor
{
public
GreetingActor()
{
Receive<string>(
s
=>
Console.WriteLine(“Hello
”
+
s));
}
}

34. step 2
create an actor

35. var
system
=
ActorSystem.Create(“GreeterSystem”);
var
greeterActor
=
system.ActorOf<GreeterActor>();

36. greeteractor isn’t
something you can call
normally
it’s a reference to an actor

37. where is my
actual actor?
AKKA.net
root actor
your
actors

38. Addressable like a file
system or web site
akka://Greetersystem/user/parent/child

39. step 3
send a message

40. greeter.Tell(“DDDSW”);

41. step 4
change behaviour

42. Visual studio
based demo

43. resilience in
reactive systems

44. WE want
applications to
ISOLATE ERRORS
SELF HEAL

45. your users don’t
want to see THIS

46. Service aService B
supervisor
Request
Response
user error
error action

47. scalability in
reactive systems

48. scale up has a
ceiling
scale out doesn't

49. and it’s easy
if you share nothing

50. how do we handle
increased load?

51. pools of actors

52. visual studio
based demo

53. how do we use
akka.net

54. the internet of
things

55. what is the Iot?
pointless
A security nightmare
i really don’t want to be facebook
friends with my toaster

56. managing farms

58. some things we
saw

59. actors are cheap
DON’t worry about having too many

60. Always take back
pressure seriously
LIBRARIES LIKE POLLY HELP

61. LET IT CRASH
don’t worry about catching all
exceptions

62. message passing is
harder to debug
use akka.testkit to comprehensively
test

63. understand message
delivery guarantees
at most once is default
at least once is an option

64. IN conclusion

65. akka.net gives us
lots
Auto-scaling
Service discovery
SELF HEALING
CLUSTERING SUPPORT
CQRS
MESSAGE PASSING LOCATION TRANSPARENCY
CONFIGURATION

66. MAKES IT EASIER TO
build reactive systems

67. understand the
difficulties

68. where next?

69. WANT TO
contribute?
github.com/akkadotnet/akka.net
gitter.im/akkadotnet/akka.net

70. want some help?
https://petabridge.com
HTTPS://github.com/petabridge/akka-bootcamp

71. read the book
http://manning.com/brown2
coming later this year

72. Q&A