Additional Storage space for 1and1 Cloud Servers
In the Cloud Server industry there’s a few things that are trending when dealing with the ever growing needs of services being in “the cloud.” One of those trends are “Block Storages” in which companies like AWS and Digital Ocean offer a means of having a storage container for use in your cloud architecture. Traditionally with Cloud Servers and Virtual Servers you had to increase your package’s overall resources to benefit from additional diskspace, which lead to a pollution of unneeded vCores or Ram just to get more space.
1and1 has a few methods to overcome these challenges: Flex packages and Shared Storage.
As we mentioned, the traditional idea with Cloud Servers and Virtual Servers were that you chose a package of predefined limits, just like you would with all Servers, but you could increase these limits by moving up to a higher package. Traditional Bare-Metal Servers required you to upgrade to a whole new server to increase CPU, RAM, or Diskspace, whereas Virtual Servers and Cloud Servers allowed you to just choose the next level or package and your limits would just change to those. To ensure proper management of resources on nodes, most companies require you to stick with these packages and don’t allow for deviation. Their whole math is based off of how many “M”, “L”, “XXL” servers they can fit before needing to move the VMs/Containers to a new node.
Fortunately, 1and1 Cloud Servers offer the possibility for flexible configurations along side their pre-defined packages which they call “Flex” packages. At any time, a pre-defined server like an “M” with 1vCore, 1GB of Ram, and 40GB of SSD could become a Flex with the same configuration and then each individual resource could be expanded. So say you need 1vCore, 1GB of Ram, and 500GB of SSD for a backup repository server, then that’s simply a button push away. If you find that your Flex matches a pre-defined configuration, then you can flip the switch and change to that Package.
A common experience I’ve seen is people who after increasing their SSD to that of a package size, felt that they could benefit from the increase of RAM and vCores as well and simply changed back over and reaped the benefits of the price. Then when more SSD was required, they flipped back over to Flex, increased the SSD, and continued from there.
Flex Packages cost $7.20 per vCore, $7.20 per GB of Ram, and $7.20 per 100GB.
M Package (1vCore, 1GB Ram, 40GB SSD) = $9.99 ($17.28 for Flex)
L Package (2vCores, 2GB Ram, 80GB SSD) = $19.99 ($34.56 for Flex)
XXL Package (4vCores, 8GB Ram, 160GB SSD) = $49.99 ($97.92 for Flex)
Obviously if your requirements fit that of a Pre-defined package, the benefits are there to stay with it. But imagine if you’re an L package and needed 160GB of SSD. You can either choose XXL Package which benefits you with 2 more vCores and 6more GB of Ram or you can go with a Flex.
Flex 2vCores, 2GB Ram, 160GB SSD = $40.32.
As your project grows in needed SSDs but doesn’t grow in compute or memory, the Flex starts to shine. It’s a “pay what you need” plan.
1and1 has also released the idea of having a Network-attached File System which can be attached to any number of servers. Here, just like from AWS and DigitalOcean, you’re paying for Diskspace and no other factors. DigitalOcean and AWS’s General Purpose SSD (“EBS”) costs $0.10 per GB. At 1and1, they sell the same functionality for $7.20 per 100GB or $0.072 per GB, and it can be attached to any and all cloud servers on your contract.
Use Cases of Flex Packages
So as we already know, you can change your current server to becoming a Flex and increase its drive space and you can even add additional SSD drives (up to 8) for a total of 4TB. I’ve found though that most of the time I want my frontend webservers to stay with the normal packages (typically L packages) and then create my database servers and backup servers as Flex packages.
Backup Server | SFTP / FTP storage
Flex Server with 1vCore, 500MB (0.5GB) of Ram, and 500GB of Storage.
Since it’s a normal server, I can deal with authentication as I see fit. The server remains on a private network with no outside network capabilities.
DigitalOcean or AWS cost: $50.0/month with no local OS (and limited to being connected to 1 droplet)
Database Server | Maria Cluster
Flex Server with 2vCores, 2GB Ram, and 200GB of Storage
A normal server with just private networking, configured for Master-Master Clustering.
Cost: $43.20/month per DBServer (+ $4.99 for a HAProxy Server for loadbalancing additional DBServer)
1and1 Total: DBServer + HAProxy = $48.19
DigitalOcean and AWS: $20/month for the storage.
Then need to configure your DB Servers and HAProxy Node: $20/month for 1DB server (2vCores, 2GB Ram, and 40GB SSD) + $5 for the HAProxy Node (1vCore, 0.5GB ram, 20GB SSD)
DigitalOcean Total: DBServer + HAProxy + 200GB BlockStorage = $45
DigitalOcean Limitation: Each DBServer needs its own BlockStorage!