By mikel965814
Suppose I have customers using my web app, and there’s no overlap in customer data, so no shared database is required. This means I could spin up a Droplet for each customer.
Seems like there could be a number of advantages:
I’d think the tradeoff of this approach versus a single high capacity server might be administration overhead ( and possible additional cost ) of multiple Droplets.
Has anyone looked at this tradeoff and decided why one approach might be better?
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
If you plan on a good number of users using your web app, I’d recommend scaling out from the start. Why? Because of the way DO handles disk upgrades.
To upgrade CPU & RAM, all you’re troubled with is a reboot; quick and easy. For disk, it’s shutdown, snapshot, deploy snapshot to a new Droplet, potentially lose the current IP and in the process, hope you don’t have to reconfigure the network each time as it’ll become a PITA.
I would normally recommend learning to manage LXC/LXD containers (Linux Containers), though with the disk upgrade “issue”, this would be a bit of a nightmare and would spell downtime for many.
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
Full documentation for every DigitalOcean product.
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
Stay up to date by signing up for DigitalOcean’s Infrastructure as a Newsletter.
New accounts only. By submitting your email you agree to our Privacy Policy
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.