Diese Präsentation wurde erfolgreich gemeldet.
Wir verwenden Ihre LinkedIn Profilangaben und Informationen zu Ihren Aktivitäten, um Anzeigen zu personalisieren und Ihnen relevantere Inhalte anzuzeigen. Sie können Ihre Anzeigeneinstellungen jederzeit ändern.
@petabridge Petabridge.com
Internals: How Akka.Remote
Connections Work
By Aaron Stannard
CTO, Petabridge
@petabridge Petabridge.com
Sample Configuration
@petabridge Petabridge.com
Terminologies
@petabridge Petabridge.com
Initial State
@petabridge Petabridge.com
Connecting to Remote Systems
@petabridge Petabridge.com
Inbound vs. Outbound
Endpoints
@petabridge Petabridge.com
Associating
@petabridge Petabridge.com
Akka Handshake Protocol
@petabridge Petabridge.com
Why do we bother?
@petabridge Petabridge.com
Remoting System Actors
@petabridge Petabridge.com
EndpointManager
@petabridge Petabridge.com
Endpoint Policies
@petabridge Petabridge.com
Writing to Endpoints
@petabridge Petabridge.com
Reading from Endpoints
@petabridge Petabridge.com
Disassociation
@petabridge Petabridge.com
Akka.Remote Training
https://petabridge.com/training/akk
a-remoting/
Nächste SlideShare
Wird geladen in …5
×

Akka.NET Internals: How Akka.Remote Connections Work

1.089 Aufrufe

Veröffentlicht am

Akka.NET Internals: How Akka.Remote Connections Work

Walks through associations, endpoints, and other Akka.Remote terminology.

Want more information on Akka.Remote? Check out Petabridge's Virtual Training on Akka.Remote:

https://petabridge.com/training/akka-remoting/

Akka.Remote System Actors
--------------------
/system – System Guardian. Built into Akka core.
- /transports – Transport Supervisor. Responsible for restarting transports if they fail and creating the Akka Protocol Manager.
- /akkaprotocolmanager – responsible for ensuring that the Akka Protocol handshake + heartbeats are initialized for every endpoint created on top of a specific transport
- /akkaProtocol – the ProtocolStateActor instance responsible for heartbeats and handshakes for the specific endpoint
- /endpointManager – Endpoint Manager. Starts all transports, creates all endpoints, responsible for applying policies to endpoints, and first responder to inbound association requests.
- /reliableEndpointWriter - ReliableDeliverySupervisor – used by outbound endpoints to guarantee delivery of messages needed to complete the Akka Protocol Handshake.
- /endpointWriter – Endpoint Writer. Writes outbound messages to the underlying transport and handles serialization.
- /endpointReader – Endpoint Reader. Receives inbound messages from the underlying transport, deserializes them, and dispatches them destination actors.
- /remote – Remote Daemon. Creates remotely deployed actors.
- /remote-watcher – Remote Deathwatch. Extends Deathwatch capabilities to actors running on other systems.

Veröffentlicht in: Software
  • Login to see the comments

  • Gehören Sie zu den Ersten, denen das gefällt!

Akka.NET Internals: How Akka.Remote Connections Work

  1. 1. @petabridge Petabridge.com Internals: How Akka.Remote Connections Work By Aaron Stannard CTO, Petabridge
  2. 2. @petabridge Petabridge.com Sample Configuration
  3. 3. @petabridge Petabridge.com Terminologies
  4. 4. @petabridge Petabridge.com Initial State
  5. 5. @petabridge Petabridge.com Connecting to Remote Systems
  6. 6. @petabridge Petabridge.com Inbound vs. Outbound Endpoints
  7. 7. @petabridge Petabridge.com Associating
  8. 8. @petabridge Petabridge.com Akka Handshake Protocol
  9. 9. @petabridge Petabridge.com Why do we bother?
  10. 10. @petabridge Petabridge.com Remoting System Actors
  11. 11. @petabridge Petabridge.com EndpointManager
  12. 12. @petabridge Petabridge.com Endpoint Policies
  13. 13. @petabridge Petabridge.com Writing to Endpoints
  14. 14. @petabridge Petabridge.com Reading from Endpoints
  15. 15. @petabridge Petabridge.com Disassociation
  16. 16. @petabridge Petabridge.com Akka.Remote Training https://petabridge.com/training/akk a-remoting/

×