Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

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?