can you get the availability you want by just putting a load balancer in front of say three instances of memstate and configure two in some type of slave setup, so if a node goes down the load balancer tells the slave, you're it?
This is exactly how OrigoDB works. There is one primary and 0 or more replicas. The nodes talk to each other. Memstate is different. It relies on the underlying storage for ordering guarantees, nodes don't talk to each other.
I've found this while we were chatting which is either marketing bullshit, or possibly something we could use?
Azure Storage simplifies cloud development
The Azure storage service supports all three strategies, although it is distinctive in its ability to provide full support for optimistic and pessimistic concurrency because it was designed to embrace a > strong consistency model which guarantees that when the Storage service commits a data insert or update operation all further accesses to that data will see the latest update. Storage platforms
that use an eventual consistency model have a lag between when a write is performed by one user and when the updated data can be seen by other users thus complicating development of client > applications in order to prevent inconsistencies from affecting end users.