6 ms·
Like all DigitalOcean products, the App Platform provides predictable, easy-to-understand pricing that allows you to control costs to prevent surprise bills. I
by onion2k 6y ago
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.
- phildougherty 6y agoThanks for the feedback! Autoscaling is not yet supported on the platform (but is coming soon). Before autoscaling lands as a feature, insights based alerting will also land. You'll be able to setup alerts for scaling events, bandwidth, cpu, memory, and more that can be sent via email or slack.
- onion2k 6y agoMy point is that alerts aren't really enough. If I'm asleep or on a plane or something then it could be many hours before I even see an alert, by which time it's probably too late. I'd prefer to be able to set up rules beforehand that prevent an unforeseen bill. If the App Platform doesn't have that feature, and it isn't planned, that's OK but I'd argue that isn't really preventing a surprise bill as the marketing site claims. A warning isn't quite the same as prevention.
- garettmd 6y agoMost autoscaling platforms let you define min and max types of restrictions. I assume DO would have the same functionality in their autoscaling.
- bravura 6y agoCorrect me if I'm wrong, but AWS doesn't allow you to do hard limits. I was creating a public S3 bucket today and wanted there to be a hard limit, so I couldn't get slapped with a huge AWS bill. Looking at the docs, it appears I can get alerts but not set a hard limit on my billing.
- user5994461 6y agoAWS allow to set limits on autoscaling groups, ECS, EKS. All the things with autoscaling really. If you're worried about billing, S3 is not a great choice. S3 is precisely unlimited storage for enterprise.
- SahAssar 6y agoSaying that something that is billed based on usage is not also able to have it's usage capped seems weird.
- phildougherty 6y agoSorry, I think I misunderstood what you were saying there. Could you clarify a bit more about what kind of functionality you'd prefer we support in the scenario you described? A large influx of traffic hits your application while you are unavailable to handle it. If you do not have autoscaling enabled, your application performance could suffer, if you do have it enabled your bill could grow out of bounds. We do plan to let you set min and max bounds for autoscaling once it is implemented. Thanks for your help!
- onion2k 6y agoWe do plan to let you set min and max bounds for autoscaling once it is implemented. This is exactly the sort of thing I'm talking about, but for money rather than computing resources or bandwidth. I'd like a feature that where the requirement is effectively "Fall back to a serving sorry-I'm-poor.html instead of the app if the total monthly bill has exceeded $xxx". For a side project I'm more interested in not paying an unexpected bill than getting traffic.
- mrkurt 6y agoFor what it's worth, we (Fly.io) have this feature, and announced it as part of our launch post on HN. But literally no one has asked us to enable it on their apps. So we never made it self service. I think for most companies, it's better to set the expectation that the service costs money, bursts will cost more money, and then forgive outlier charges once or twice. It's tremendously difficult to compete against the AWS's of the world, putting work into features specifically to minimize how much people spend seems like a good way to fail a company.
- the_duke 6y agoI'd argue that many users that end up with surprise bills are either inexperienced or are deploying something small without giving it much thought. In those cases, the users will either not know or not think about such expense limits. The solution is to set relatively strict limits by default and even occasionally warn users about unused/underutilized resources. But as you said: such features are bad for the bottom line . And I can appreciate the enormous difficulty of competing with the big 3.
- p410n3 6y agoWhat good are alerts when I sleep? I usually don't even check my personal mail until I'm done at work. There's a lot that can happen in 16h
- rgbrenner 6y agoOn AWS I tie high billing threshold alerts with PagerDuty so it wakes me up at night.
- tupputuppu 6y agoOh man, what a user friendly solution
- mariushn 6y agoWe need limits, not alerts. That is, autoscale up to X.
- phildougherty 6y agoThanks for the clarification. We do plan to implement hard limits in the autoscaling feature.
- names_are_hard 6y agoI've said this elsewhere in this thread, but there's a difference between predictable pricing and controlling runaway costs. Predictable pricing means that each month my bill is the same: I'm on a $15 plan, I pay $15 a month. No nickel-and-diming, no hidden fees, life is simple. This is a good thing. Controlling costs means that no matter what happens, my costs will not exceed $x/month. Service might degrade if necessary, but I will not pay for anything above some upper limit. Seems that DO has the former but not the latter, because if things get out of hand (caused by an attack, a bug in my code, going viral) the customer can be stuck with a bill. Alerts do not alleviate this risk. Pricing that is generally predictable does not alleviate this risk. Only a hard cap does. I want a plan that says "you have 250 GB of traffic, after which requests will fail and you'll get an email". You can make it nicer by sending me a warning email at 200GB so that I have time to upgrade my plan if I want.
- crazygringo 6y agoThat seems somewhat opposite to the point of PaaS, no? If you want controllable costs and you don't want people using your service because interest explodes, then just stick to a regular droplet, no? The entire point of this is that if usage explodes, you want to pay to support that usage. That's the entire feature. (Also, HN frontpage traffic isn't that much -- it's a few requests per second at most, not thousands per second.) The only scenario I can imagine where this would be a genuine concern would be if you were subjected to a (D)DoS-type attack. But in that case you still want legitimate users to get through, so you really need a separate DoS-protection layer which is totally orthogonal to this. Am I missing something?
- phildougherty 6y agoA little tidbit: everything you deploy on App Platform comes with DDoS protection built in.
- adkadskhj 6y ago> That seems somewhat opposite to the point of PaaS, no? Why would that be true? I thought the point of a PaaS was getting a Platform - as a Service. I don't interpret that to mean having no control or limits on potential costs. To me a PaaS is about not wanting to manage a the metal or infra under the app. Which i don't think is misguided or inaccurate. To look at it differently: I am a customer to someone. I am a customer who wants to buy a product that manages all of the infra for my application. I also have a limited budget, and the notion of an unlimited budget is an instant no for me. Call the XaaS whatever you like, but my motivation is clear. Maybe DO doesn't want me as a customer (if what you say is true about PaaS), but i think there's opportunity there for a new XaaS.
- pomatic 6y agoThis 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.
- WrtCdEvrydy 6y agoThis 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.
- pomatic 6y agoTo 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.
- WrtCdEvrydy 6y agoI 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"
- tidepod12 6y agoWhat 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.