Comment by ufmace
4 years ago
Very interesting that this feature is often demanded in tones of righteous outrage on posts about autoscaling cloud services, yet when actually implemented, nobody has actually set it up.
4 years ago
Very interesting that this feature is often demanded in tones of righteous outrage on posts about autoscaling cloud services, yet when actually implemented, nobody has actually set it up.
> So we never made it self service.
I may not underestand parent, but it sounds like its not equivalent to a button next to the auto-scale but more like an email and pre-requisite knowledge that it exists?
Yes we advertised it as a feature to all new signups, with a link to request limits. It's not equivalent to a button, the dirty secret is that when people requested it, I planned to put a notification in my calendar to go look at their usage the last day of the month and adjust their bill accordingly. :)
We were concerned about spending time on marginal features that didn't actually matter much to people, so we "launched" it without building it to see if anyone cared.
I'm not one of your customers but when I have looked at pay-as-you-go services or autoscaling services before I basically don't even consider any that don't allow me to cap the costs per month or similar.
So you could perhaps also consider that if it is only marketed when you sign up and not a clearly defined feature some people (like me) will just never sign up at all.
3 replies →
I’m also not interested in this feature, but do want to say that’s a lovely example of implementing the bare minimum to gauge the value of a feature.
That was a great MVP plan for that feature! Figuring out what not to build is a great way to save development time.
In addition to there being no self-service, the kinds of people who want this aren't going to be using Fly.io in the first place. Look at the prices. DigitalOcean's $5 droplet would cost over $50/month on Fly.
That's not true. Our CPU VMs are similar to DO's CPU optimized droplets. The cheaper droplets are all shared CPU.
No, what I wrote is true based on the info listed on fly.io. Either those prices and specs are incorrect, or your comment is narrowly focusing on the CPU axis (which still doesn't make for a good comparison, considering the options Fly gives are $2.67 or $8) and calling it sufficient. DigitalOcean's cheapest droplet comes with 1GB RAM, whereas to match that with Fly, that's $35 minimum. You don't get to ignore that. Add in the costs listed under Fly's "Network prices" and we're nowhere close to $5.
If for some convoluted reason this is wrong, then you guys really need to reconsider how you're presenting your prices and to lay out exactly what those convoluted reasons are, because Fly's pricing page certainly tells people that trying to match DigitalOcean's $5 plan is going to cost 10x on Fly.