Droplets best practices

I’ve finally on boarded with Digital Ocean. I created an Ubuntu Droplet which I plan on using for hosting my Go application. I would like to use Gitlab as part of my git ecosystem as well.

Should I create a new droplet with the GitlabCE application image? or Should I just upgrade my current droplet and install via curl? What are the advantages or disadvantages of using a single droplet to handle multi-tasks? Should I be using a droplet to handle my Go app and hosting and a separate droplet for GitLab hosting?

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.

@michael, Thanks for your input. I had a hunch that keeping everything in separate droplets would also be more modular, but I’m fairly new to all of this cloud VPS, so I wanted a consensus. I think you hit on some key points. Thanks again.

I tend to like splitting up different functions into different servers. This allows the server to concentrate on only performing one task. For example my current setup is a separate server for Gitlab, App Server and DB server. It is also nice because later if I expand I can just create a snapshot of the App server and deploy it as a second droplet. i do not have to worry about it also cloning the Gitlab instance and then having to remove it. <br> <br>I think ultimately it is personal preference.