Firewalls place a barrier between your servers and other machines on the network to protect them from external attacks. Firewalls can be host-based, which are configured on a per-server basis using services like IPTables or UFW. Others, like Xetabytes Cloud Firewalls, are network-based and stop traffic at the network layer before it reaches the server. You can apply cloud firewall rules to individual VCS Instances, but a more powerful option is to use tags. Tags are custom labels that you can apply to VCS Instances and other Xetabytes resources. When you add a tag to a firewall, any VCS Instances with that tag are automatically included in the firewall configuration.
Xetabytes Load Balancers are a fully-managed, highly available load balancing service. Load balancers distribute traffic to groups of VCS Instances, which decouples the overall health of a backend service from the health of a single server to ensure that your services stay online. Using a load balancer as a gateway gives you the flexibility to change your backend infrastructure without affecting the availability of your services, enabling seamless horizontal scaling, rolling deployments, large architecture redesigns, and more.
Floating IPs let you redirect network traffic between any of your VCS Instances within the same datacenter. Assigning a floating IP to a Droplet doesn’t replace or change its original public IP address. You can use floating IPs to create server infrastructures without single points of failure, but a floating IP alone does not automatically provide high availability. For a setup to be highly available, you need to implement a failover mechanism to automate the process of detecting failures of the active server and reassigning the floating IP to a passive server.
When you manage your infrastructure on Xetabytes, you may find it more convenient to manage your domains here as well. Xetabytes' DNS tools allow you to manage your VCS Instances, Xetabytes Load Balancers, and DNS in the same place. These resources are integrated into the interface so they can be located more easily. You can also manage non-Xetabytes resources using Xetabytes DNS.