Akka.Net and .Net Core - Build powerful concurrent and distributed applications

2. Community Leader
https://www.facebook.com/groups/dotnetinside/
#dotnetinside
https://www.facebook.com/groups/iotinside/
#iotinside

3. Organizadores
Alexandre Brandao
LinkedIn: abrandaol
Guilherme Magalhães
LinkedIn: guilhermevpm

4. https://www.facebook.com/groups/cloudinside/
#cloudinside
https://www.facebook.com/groups/agileinside/
#agileinside

5. Trilha Agile Inside
Adriano Oliveira
LinkedIn: adrianoctoliveira
https://www.facebook.com/groups/agileinside/
#agileinside

6. Build powerful concurrent and distributed applications
Akka.Net & .Net Core
Alexandre Brandão Lustosa
Entrepreneur at Stone Pagamentos
C# .Net MCSD / MCSA DBA SQL Server IoT / C++ Developer Engineer
(21) 97367-6161 / LinkedIn: abrandaol / Twitter: @abrandaolustosa

7. Alexandre Brandão Lustosa
Twitter: @abrandaolustosa
E-mail: abrandao@outlook.com
abrandao@stone.com.br
LinkedIn: www.linkedin.com/in/abrandaol
Phone: +55 (21) 97367-6161
Senior Software Engineer with 20 years of experience in web development, transactional and distributed systems,
Microsoft C# .Net specialist and C/C ++ development for Linux Embedded and Microchip Microcontroller. Certificated
by Microsoft .Net MCSD Web Developer, MCSA Microsoft SQL Server 2012 and Microsoft IT Specialist. Founder and
community leader of InsideTech Conf.
Entrepreneur at Stone Pagamentos
C# .Net MCSD / MCSA DBA SQL Server IoT / C++ Developer Engineer
• Entrepreneur
• C# .Net
• IoT Maker
• Arquitetura de Sistemas
• Metodologias Ágeis
• Algoritmos Computacionais
• Guitarra e Violão

8. { Stone }
Temos vagas para
Nerds Loucos!!
Great code
starts with
amazing
people
https://jobs.kenoby.com/enter.stone

9. Agenda
Introduction and concepts
Actor Systems
Akka.Net Open Source Library
Akka.Net SDK
Networking and Remoting
Clustering
Using Akka.net

10. Introduction and Concepts
Distributed Systems

11. Distributed systems
A distributed system is a model in which
components located on networked computers
communicate and coordinate their actions by
passing messages

12. Parallel and distributed computing
In parallel computing, all processors may have access to a
shared memory to exchange information between
processors.
In distributed computing, each processor has its own
private memory (distributed memory). Information is
exchanged by passing messages between the processors

13. Tipos de arquiteturas de processamento de sistemas

15. Actor Systems

16. Origem
The actor model originated in 1973. It has
been used both as a framework for a
theoretical understanding of computation
and as the theoretical basis for several
practical implementations of concurrent
systems
The characteristics of today's computing
environments are vastly different from the
ones in use when the programming models of
yesterday were conceived. Actors were
invented decades ago by Carl Hewitt.

17. Fundamental concepts
The actor model adopts the philosophy that everything is
an actor. This is similar to the everything is an object
philosophy used by some object-oriented programming
languages.

18. Fundamental concepts
An actor is a computational entity that, in response to a message it
receives, can concurrently:
Send a finite number of messages to other actors
Create a finite number of new actors
Designate the behavior to be used for the next message it receives

19. Messaging in OOP

20. Messaging

21. Ecosystems

23. Concurrency vs. Parallelism

24. The are differences
Microservices
vs
Actor Model

25. Microservices
Are a way to organize software by splitting each
area of concern into its own deployable artifact

26. Microservices

28. Microservices

29. Actor Model
Is a lower level than the
deployable artifact, more
about what types of objects
you've implemented the
service with

30. Actor System
An ActorSystem is a
heavyweight structure
that will allocate 1...N
Threads, so create one
per logical application.

31. Actor System
Workflow

32. Supervision
Dependency relationship between actors: the supervisor
delegates tasks to subordinates and therefore must respond to
their failures.

33. Akka.Net
Open Source Library
for Actor Model

34. Community-driven port
Akka.NET is a community-
driven port of the popular
Java/Scala framework Akka
to .NET.

35. Oficial Site
https://getakka.net

36. Akka.Net is Open Source
https://github.com/akkadotnet/Akka.NET

37. Reactive Manifesto
Akka.NET adheres to the principles
defined by the Reactive Manifesto.
The Reactive Manifesto proposes a
coherent approach to systems
architecture in order to build
systems that are more robust, more
resilient, more flexible, and better
positioned to meet modern
demands.

38. Microsoft Actor Model
A straightforward approach to building distributed,
high-scale applications in .NET
https://dotnet.github.io/orleans/

39. Outras liguagens

41. Documentação
https://getakka.net/articles/intro/what-is-akka.html

42. Akka.Net SDK

43. Nuget Akka.Net SDK
Install-Package Akka
Install-Package Akka.Remote
Install-Package Akka.Cluster
Install-Package Akka.Logger.NLog

44. Receive Actors
There are two types of ReceiveActor in Akka.Net
Typed Receive Actor
Untypes Receive Actor

45. Typed Receive Actor

46. Untyped Receive Actor

47. Simple example
1) Define entity/mensage:

48. Simple example
2) Define a Actor:

49. Simple example
3) Actor System, Actor and send a message with Tell():

50. Routers

51. Routing Strategies
 RoundRobin
 Broadcast
 Random
 ConsistentHashing
 SmallestMailbox

52. RoundRobin

53. Broadcast

54. Random

55. ConsistentHashing

56. SmallestMailbox

57. Dynamically Resizable Pools
akka.actor.deployment {
/my-router {
router = round-robin-pool resizer {
enabled = on lower-bound = 1 upper-bound =
10
}
}
}
The following settings are used to fine-tune the resizer and are considered good enough for most cases,
but can be changed if needed. Rules: https://getakka.net/articles/actors/routers.html

58. Networking and Remoting

59. Akka I/O
The I/O extension provides an non-blocking, event driven API that
matches the underlying transports mechanism.

60. Akka I/O
Client connection Server connection

61. Actor Path
Actor have a unique address

63. Actor Path

64. Akka Remoting

65. Built-in Transports
HOCON Config

66. Sending message on network

67. Akka.net Remoting

68. Using SSL

69. Remote Deploy
That's right - we can deploy code over the network with Akka.Remote.
Deploying an actor means two things simultaneously:
•Creating an actor instance with specific, explicitly
configured properties
•Getting an IActorRef to that actor

70. Remote Deploy

71. Clustering

72. What is a “Akka Cluster“?
A cluster represents a fault-tolerant, elastic, decentralized
peer-to-peer network of Akka.NET applications with no
single point of failure or bottleneck.
• Fault-tolerant: clusters recover from failures (especially network
partitions) elegantly.
• Elastic: clusters are inherently elastic, and can scale up/down as
needed.
• Decentralized: it's possible to have multiple equal replicas of a given
microservice or piece of application state running simultaneously
throughout a cluster
• Peer-to-peer: New nodes can contact existing peers, be notified about
other peers, and fully integrate themselves into the network without any
configuration changes.
• No single point of failure/bottleneck: multiple nodes are able to
service requests, increasing throughput and fault-tolerance.

73. Akka Cluster

74. Configuring Cluster
1) Install-Package Akka.Cluster
2) Configure seed nodes
3) Client seed nodes

76. Routes

77. System Actor Seed Node

78. System Actor NonSeed Node

79. Using Akka.net

80. CryptoCurrencyInfo
REST
API

81. CryptoCurrencyInfo
https://github.com/alexandrebl/CryptoCurrencyInfo

82. Keep in touch
 abrandao@stone.com.br
 (21) 97367-6161
 LinkedIn: abrandaol
 Twitter: @abrandaolustosa

83. Obrigado!!