Droplet's transfer limit with managed database

Posted June 5, 2019 2.8k views


question about a droplet’s transfer limit:

From what I understood, solely outbound transfer with a public network will count against the transfer limit, while transfers within its private network (i.e. with another droplet) is excluded.

If I use a managed database on the same account, is it possible to use it within a private network with my droplet, so that a communication between the two will not be counted against the transfer limit at any time?


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.

Submit an Answer
4 answers

Ok great! So then no communication between the two would be counted against the transfer limit? And the transfer limit would only be counted against when data leaves my droplet outside the private network?

Say a user requests data from my db. He would call my droplet api, my droplet will process the request and query the db, my db will respond to the droplet and my droplet will forward the data to the user.

Since the droplet and the managed db are in a private network, the total transfer would only be counted against one single time, being the moment my droplet sends the data back to the user, correct?


Hey there,

You can enable private networking on your Managed Database to enable connectivity over the private network instead of the public network! You’d just need to use the private connection string from a Droplet with private networking enabled in the same datacenter as your cluster.

Ethan Fox
Developer Support Engineer II - DigitalOcean

That’s correct (at least as I understand it), although technically the initial request coming in would count as well as the response. Just not the traffic between the database and the droplet.