How transfer is charged?

Hi, I have a question about transfer charging. If I buy 4 droplets of 5USD each one having a transfer of 1TB Transfer I will have to pay 4 x 5 = 20 USD monthly. Those 4 droplets will name A, B, C i D. Here is deployment layout:

/----- B / A ------- C
----- D

On A is load balancer and on B, C & D are web servers. Droplet A is only one accessible from outside. Imagine I have 3TB transfer via A. 1TB is distributed via AB, 1TB via AC and 1TB via AD. How I will be charged? I have 4 droplets each of 1TB transfer which in total is 4 TB but on the other side droplet A come with 1TB only. Can I count on $TB transfer in this situation or only 1TB? If interdroplet transfer is not charged how this relates with total transfer? Does those 20USD are enough for this month and 3TB or transfer or I will be charged for 2TB above on droplet a?

Best, Dragan

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.

I think the Digital Ocean platform would be a lot more attractive to high traffic architectures if the sum of all droplet-transfer could be added up to a total. Where this total transfer is consumed shouldn’t matter.

Say for example I have a high traffic site that needs 8 webserver droplets of 1GB that serve the webpages (internally). An in front of those I’d need a load balancer droplet of 1GB that distributes the incoming requests over the webserver droplets.

So all public traffic goes through the load balancer droplet, all communication from and to webservers is internal traffic and doesn’t count towards the cap.

Now my total public the website can serve is 2TB (since the cap of the load balancer is the only one useable). While my webservers could easily handle the needed 15TB for running my website.

The current droplet models would not even allow me to use Digital Ocean since the maximum cap is 9TB, and paying for this unneededly big machine plus the 6TB extra traffic is unattractive.

Alternative would be to us DNS load balancing but that is undesirable because of the inflexibility and dependence on how clients handle receiving multiple IPs for a name.

How would you architect a high traffic website on Digital Ocean? Maybe I’m just overlooking some options :-)

Regards, Jacco

Kamal, <br>in other words this mean that I will have to pay for additional 2TB? <br>In my case all outbound trafic is via droplet A so I will be charged for 2TB over?