Akka.NET Internals: How Akka.Remote Connections Work
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.
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Mehr von petabridge
Mehr von petabridge (13)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Akka.NET Internals: How Akka.Remote Connections Work
- 1. @petabridge Petabridge.com Internals: How Akka.Remote Connections Work By Aaron Stannard CTO, Petabridge
- 5. @petabridge Petabridge.com Connecting to Remote Systems
- 6. @petabridge Petabridge.com Inbound vs. Outbound Endpoints
- 8. @petabridge Petabridge.com Akka Handshake Protocol
- 9. @petabridge Petabridge.com Why do we bother?
- 10. @petabridge Petabridge.com Remoting System Actors
- 13. @petabridge Petabridge.com Writing to Endpoints
- 14. @petabridge Petabridge.com Reading from Endpoints
Hinweis der Redaktion
- /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.