Question
Huge divergence in bandwidth allotment between app platform and regular droplets
- Posted on January 15, 2021
- DigitalOcean App PlatformNetworkingDigitalOcean Managed Kubernetes
Asked by cemerick
In evaluating app platform, I am struck by the huge divergence between the reasonably generous outgoing bandwidth allotted cumulatively based on the number of “regular” droplets one pays for, vs. the very small and inelastic bandwidth allotment on the app platform.
In summary:
- if we pay for e.g. 5 of the cheapest droplets, we get 5,000 GB of outgoing bandwidth (and this applies if the droplets are part of a k8s cluster as well).
- if we have a single app platform deployment, it could utilize any number of droplets; its outgoing allotment would only ever be 100 GB outgoing
Can someone explain the rationale for this, especially in light of app platform nodes’ much higher cost vs. equivalent regular droplets?
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.
Hollie's Hub for Good
Working on improving health and education, reducing inequality, and spurring economic growth? We’d like to help.
Get started for free
Enter your email to get $200 in credit for your first 60 days with DigitalOcean.
New accounts only. By submitting your email you agree to our Privacy Policy.
Turns out this was addressed in an answer from @phildougherty to a question posed in October on the same topic:
I don’t quite understand what math could lead cloudflare service to increase effective costs so dramatically, but in any case: I’ll second the further replies on that thread that the integrated CDN is of minor interest, especially given the additional costs it apparently implies.