Sodacan
MavenSystem View
This covers the system, non-functional view of Sodacan.
Picture here: Top is a Sodacan cluster, level 2 a host, a configuration, and a coordinator off to the side. level 3 is Actor groups and a scheduler off to the side Level 4a ActorEntry on top of Actor Level 4b is Actor and Message Level 5 is Persistors, Serializers and Jugs
Host
A Sodacan Host temporarily hosts one or more ActorGroups. ActorGroups can (and should) be replicated for durability. The configuration can specify the number of ActorGroup replicas to maintain including what it takes to maintain a quorum.
Coordinator
Sodacan is a peer-to-peer network. No single point of failure. It is common to operate at least two hot replicas for any given ActorGroup. Additional “cold” replicas can also be configured. Cold replicas require less compute but take longer to come on-line. Having only a single copy of any particular ActorGroup is not durable or fault-tolerant. A minimum of three ActorGroup replicas, each on a different Host, are required for durability. But the number can be much higher as needed for horizontal scaling.
Load Balancing
As is common in such systems, a load balancer will provide the user with access to more than one web server. Internally, Sodacan makes no distinction about which Host's web server a request originates from: The host will route the request just like any other message in receives.