Most active commenters
  • pomatic(4)
  • WrtCdEvrydy(3)

←back to thread

DigitalOcean App Platform

(pages.news.digitalocean.com)
646 points digianarchist | 15 comments | | HN request time: 0.204s | source | bottom
Show context
onion2k ◴[] No.24698869[source]
Like all DigitalOcean products, the App Platform provides predictable, easy-to-understand pricing that allows you to control costs to prevent surprise bills.

I can't see any features listed that enable me to control costs to prevent surprise bills. If a site got submitted to HN and hugged to not-to-death-because-it-autoscales then I'd wake up to a bunch of alerts and massive outbound bandwidth bill. I don't want that. I want something that stops that happening.

replies(3): >>24698927 #>>24700146 #>>24700352 #
1. pomatic ◴[] No.24700352[source]
This is laughable - billing is logically separated from droplet use, so unlike other providers DO charges for the potential to use a capability, rather than actual use, regardless of whether it is consumed. I got stung badly by this - charged for X droplets capability when zero droplets capability was being used for several months. Explained the misunderstanding to DO, got no sympathy & no refund. Won't touch them again, don't trust them further than I could throw them.
replies(2): >>24700752 #>>24700952 #
2. WrtCdEvrydy ◴[] No.24700752[source]
This is what makes "the cloud" profitable.

If your droplet isn't using all of it's resources (CPU, RAM, DISK), they are able to oversell their capacity.

replies(1): >>24700828 #
3. pomatic ◴[] No.24700828[source]
To be clear, I had no deployed resources, but was still charged as if I had. As it turns out, it's impossible to cancel the "standing charge" without recourse to support.

There's a difference between load balancing of shared resources and (what I believe must be) deliberately deceptive practices. A customer-centric company would send an email to notify you of this kind of over-charging.

It's premeditated and dispicable.

replies(2): >>24701054 #>>24701109 #
4. ohgodplsno ◴[] No.24700952[source]
You bought access to X servers knowingly (because you can't do that by accident), let them sit here knowingly, then got billed the exact number that was listed, but somehow that's DigitalOcean's fault ?
replies(1): >>24701228 #
5. WrtCdEvrydy ◴[] No.24701054{3}[source]
I didn't say it wasn't a shitty outcome, but this is what people advocate for when there's a push "for the cloud" or "how aws is doing great things"
6. tidepod12 ◴[] No.24701109{3}[source]
What you call "premeditated and despicable" is actually a huge value proposition for others. Whereas AWS/GCP have pricing structures based on usage and you never know until the end of the month how much you owe, DO instead has defined "you will pay $50/mo for this regardless of if you do or do not use it" and from what I've seen, many people really value and appreciate that, and specifically choose DO over AWS/GCP because of that.

The pricing model for App Platform seems antithesis to that, though, which is interesting. DO is becoming more like AWS/GCP with every feature release, which I don't necessarily find to be a good thing.

replies(1): >>24701210 #
7. pomatic ◴[] No.24701210{4}[source]
The problem I have is not with the model, but with the fact it is so difficult to cancel the standing charge. If it could be done from the web UI, and/or there was an interlinked pop-up when zero droplets are deployed, fine.
replies(1): >>24703989 #
8. pomatic ◴[] No.24701228[source]
> let them sit here knowingly

Nothing was deployed. Zip, zero, zilch resources were used month-on-month. My fault, yes, but naively I assumed if this was the case, billing would automatically drop to zero.

Whilst I bought access to X servers but had no way to remove the charge associated with that without contacting customer services when I decided X=0, permanently.

I mean, really? I have no problem with PAYG or PAYG to a capped amount, but PAYG for a fixed amount regardless of whether or not the resources are actually deployed is disingenuous at best.

replies(2): >>24701374 #>>24701413 #
9. hundchenkatze ◴[] No.24701374{3}[source]
> Nothing was deployed. Zip, zero, zilch resources were used month-on-month.

This is like leasing a car, leaving it parked, and then complaining you have to pay the lease.

10. ohgodplsno ◴[] No.24701413{3}[source]
So, you simply did not read the pricing page, that explicitly says that it's going to bill you that, and that you do whatever you want with it. And /or have never used a VPS service before . You are quite literally renting space and CPU time on their servers, that they are keeping (mostly) free and reserved for you.

You don't complain that you were charged $200 for renting a parking space and never using it, no reason for this to be different for servers.

replies(1): >>24702361 #
11. potatohedz ◴[] No.24702361{4}[source]
Except in this case, other cars are being parked in the space when it is "empty", and you can only find the car park attendant on every third Monday in the month to rescind the agreement
12. dkersten ◴[] No.24703989{5}[source]
Wait, I'm confused. What standing charge? What exactly did you get charged for? I've been using DO for a few years and I have no idea what you are referring to. When I delete my unused resources, I don't get charged.
replies(1): >>24704849 #
13. WrtCdEvrydy ◴[] No.24704849{6}[source]
He probably forgot to turn off the instances and kept getting charged.
replies(2): >>24705923 #>>24708894 #
14. ◴[] No.24705923{7}[source]
15. dkersten ◴[] No.24708894{7}[source]
Ah, right, shutdown but not deleted. DO are upfront about that charge though and its not like its any different on any other cloud provider.