If SERVERware breaks, the system continues on its own. But you are loosing failover functionality and GUI.

SERVERware has multiple protection mechanisms to prevent this:
    - Mirroring of controller host (hosts where SERVERware is running) with drbd and heartbeat
    - SERVERware daemon has multiple processes for each functionality
        - Monitoring
        - Replication
        - Failover

These processes are monitored with an additional process, whose functionality is to reset any of these processes if they make no responses in some timeout.

It is designed to be as simple and stable as possible because SERVERware is responsible for keeping other processes doing their tasks and retries if temporary network issues appear.

SERVERware is using  tcp/ssh2 protocol to communicate with, and control hosts in the network.
The recommended configuration is to have a LAN network  which connects serverware hosts. Only VPSes and SERVERware GUI (tcp ports 80,81,443 ) should be exported to outside world.

The whole system relays on network protocols. That means that if the network is down the whole system is down.