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?
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.