Is DigitalOcean the right Hosting for this?

Hey guys sorry to bother but I have a question about digitalocean that I couldn’t find the answer to.

When you create your first droplet you start with a 5$ plan and that’s ok cause my website has low traffic right now, but what if my website jumps from 100 visits a day to 100k visits a day all of a sudden?

Do they just update my droplet and increase my billing is that it? Or do I have to set up the whole website on a new vps and all that stuff again?

I’m basically looking for a place where I can just set up my website and never have to move to another hosting again, even if it reaches like 1M views a month, does digital ocean do that?

Thanks a lot

Submit an answer

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!

Sign In or Sign Up to Answer

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.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

Short answer… No :)

Without knowing your setup (CMS, static site etc) will determine how you can scale appropriately.

DO, like other providers allow you to ‘resize’ a droplet (on-demand) so lets say you need more CPU / RAM you can resize your droplet to a faster comparable droplet (storage needs to be the same or more then the previous) This will allow you to scale vertically but this is not always the most cost effective way of doing it.

The next option would be to use multiple droplets and place a load balancer in front of it. This way the traffic will now be split between 2 (or more) droplets. The load balancer will take care of directing traffic and the IP of the loadbalancer if what you will map to allowing the LB to send traffic to each running droplet.

There is a downside to this as you are always running hot meaning your paying for the servers no matter what, spinning up new instances will be manual (from what I understanding on DO), updating can be a bit of a pain because you need to update code on all running instances and update the snapshot you base things off as well. This is where a git hook or pipeline would come in to push to each running droplet when code is committed but that can get a bit more complicated…

This brings up to containers, with DO’s new app platform you can do this fairly quickly as it will do a sort of source to image, basically taking your application, creating a docker image and deploys it to a managed Kubernetes instance, letting you add nodes when you need it and remove them when you don’t, basically allowing for horizontal / vertical scaling with no down-time. Auto scaling is in the roadmap from what I understand but this brings us back full circle as to your websites backend. If you are using something like wordpress I would not look at app platform because well, WP is dynamic, meaning you can upload images plugins etc. This can and is problematic because arguably WP does not want to be in a container. People will, and I’m sure come back and say you can do it, and yes, you 100% can run it in a container but unless you want to maintain everything via Git, offload all media to s3 or other PV it can get complicated. I have done it, still do it (work related) and I can tell you WP was not designed for a container.