High Availability

How Can I Ensure My Sockets are Highly Available?

The Border0 provisioning system is designed with redundancy and high-availability in mind.

It is recommended that every socket be served by at least 2 connectors so that in the event of a failure e.g. hardware failure, power outage, etc... your users have a way to reach their services and continue business as usual.

The choice in where and how-many connectors you deploy should be informed by your availability requirements. You may deploy connectors in different availability zones, cloud compute regions, or even cloud compute providers.

What Happens When A Connector Goes Down?

All client devices are peered with all relevant connectors at all times, even if no traffic is being sent to them. When a connector is shutdown or otherwise the Border0 control plane detects that it is offline, all client devices will be signalled regarding the event. If your sockets are served by another connector that is available, the clients will automatically use that connector.

What Happens to Existing Connections When A Connector Goes Down?

For Non-Network based sockets such as SSH, DB, HTTP, TCP servers, connections are terminated at the connector and thus if your connector goes offline, all connections will be killed as a result and your users will be kicked out mid-session.

For Network based sockets such as Subnet Routers and Exit Nodes, connections are terminated at your upstream hosts or services. This means that connectors will remain intact after a connector goes offline. In a highly-available model with multiple connectors.