Class AbstractKrouter<T extends AbstractKrouter>

java.lang.Object
org.nustaq.kontraktor.Actors
org.nustaq.kontraktor.Actor<T>
org.nustaq.kontraktor.routers.AbstractKrouter<T>
All Implemented Interfaces:
java.io.Serializable, java.util.concurrent.Executor, Monitorable, RemotedActor, ServingActor
Direct Known Subclasses:
HotHotFailoverKrouter, Krouter, SingleActiveServiceKrouter

public abstract class AbstractKrouter<T extends AbstractKrouter>
extends Actor<T>
implements RemotedActor, ServingActor
base class for load balancers and failover proxies. Krouters are designed to run as standalone processes (similar e.g. nginx). ServiceActors connect and register actively to be available. Clients connect to the Krouter which then forwards/dispatches remote messages and results depending on implemented strategy. This way services are protected against any malicious attacks as they don't even accept connections from the network (they are clients of the Krouter, the Krouter has no prior knowledge of address of the krouter's address. E.g. its possible to have a public Krouter running in the cloud and run the service behind a firewall (or even http proxy).
See Also:
Serialized Form