Repository in Server Memory

Instead of storing all of the VE's shared state in files, write a server process that simulates the behavior of a distributed file system

Each host maintains a TCP/IP connection to the server process and uses that connection to perform read and write operation on the shared state

Faster than Shared File because each host does not have to open and close each file remotely.

Don’t have to have locks. Server arbitrates.

Pros.

• The server keep the current shared state in memory

• The client no longer has to perform open and close operation on each file or unit of shared state

• The server may support batched operation (multiple read and write in one request)

Cons.

• If the server crashes, the current VE state will be lost

• Maintaining a persistent TCP/IP connection to each client may strain server resources

Support small to medium-sized net VEsn