Here are some guidelines to help you decide on whether to take servers from our public or private cloud deployment models.
Whilst our public cloud servers are fully firewalled with per-server firewall rules, ISO/PCI standards may dictate that a dedicated firewall is required and so this requires the private model.
We do not allow site to site IPsec VPNs from customer networks to the public cloud firewalls; therefore if you have a requirement for a permanent site-to-site VPN then the private cloud model is required.
Both public and private cloud deployments include SSL-VPN access for remote administration.
By default, public cloud servers cannot see each other behind the firewall. Some customers, particularly web development agencies or resellers, may want to create individual servers for their individual clients and server isolation would be preferred in this instance.
Conversely, if a customer wishes to create an infrastructure with a number of servers that can communicate securely and at 10Gb wire speeds (e.g. split web/database/file servers), a private cloud deployment with a dedicated VXLAN network segment is ideally suited to this purpose.
If a customer wishes to have multiple webservers behind a load balancer (typically with a centralised database or fileserver) then the private cloud model is required. Load balancing is not offered on the public cloud model.
In terms of server performance and scalability there are no differences between the public and private cloud deployment models.
The underlying infrastructure is the same so all customers benefit from our high performance hardware, network and storage.
Contact us to discuss your requirements.
We've got you covered
As well as 100% uptime on our CronoSphere hosting platform we can ensure that your web applications are working in an optimum manner 24x7 with true Quality of Service analysis.
Find out more