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.

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!
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.
One option would be to use DO private networking. Where one droplet would host your application server and the other would hold the database. Or maybe have your master droplet remote mount directories from your slave droplet. In both examples, you would probably want all of those resources only directly accessible behind the firewall. NOTE: private networking need to be located in the same data center, last time I looked.
Another tool to use with multiple droplets is to use DNS to seperate your URI’s, such as one droplet serving your http or https URIs, and another droplet being your ftp resource. Even though both droplets would be directly accessible, you can still use private networking between your droplets to have your server apps talk to your privately networked database.