search

heroku / roadmap

This is the public roadmap for Salesforce Heroku services.
198 stars 11 forks source link

Support for Eco dynos for Heroku Teams / Allow Dyno idling for more app types #111

Open searls opened 2 years ago

searls commented 2 years ago

Required Terms

What service(s) is this request for?

Teams

Tell us about what you're trying to solve. What challenges are you facing?

I'm a big fan of the middle ground Heroku has claimed after sunsetting free dynos & Postgres with Eco subscriptions and the PG Mini plan.

As I've worked through all my personal and work-related apps to ensure we're ready for the end of the free tier, I've decided we've gotten to the point that we should move @testdouble to Heroku Teams. However, the fact that every staging & review app would need to move to full-priced hobby dynos is holding me back from migrating to Heroku Teams.

Because our company is a consultancy, our blog (as opposed to a software product) is probably our most active Heroku app. We have dozens of consultants who contribute blog posts as pull requests for review by non-technical colleagues (for copyediting, to validate how the article looks, etc.), and Review Apps are an absolutely brilliant tool for the job. Sometimes a blog post takes several weeks or months of review and iteration before being published, so it's not uncommon for us to have relatively long-lived branches and review apps that are almost always asleep and consume very few resources.

As a result of all this, it'd really make a huge difference to our overall cost if we could leverage Eco dynos in Teams, at least for review apps and staging apps. I understand why the Free dyno tier was always excluded from Teams and Enterprise, but since Eco is a paid product tied to uptime, I think it's worth revisiting the decision and allowing them for Teams.

friism commented 1 year ago

Thanks @searls, I agree that this is something we should do. A simple way we may try to get to what (I think) you want, would be to allow dyno idling on all app types. Eg. we'd introduce a new "autosleep" scale step between 0 and 1, eg. the dyno scale slider would be: 0 -> autosleep -> 1 -> 2+.

Curious to get your thoughts on that.

searls commented 1 year ago

Anything that'll allow this sounds great to me!

jonespm commented 1 year ago

We've been trying out the Autoidle addon for the cases mentioned here. But would benefit from something more built into Heroku as you mention.

We wouldn't have to use a separate domain, could have more control over when the app sleeps and it (ideally) wouldn't be reported as an H14 critical error when it came back up.

kreintjes commented 1 year ago

Eg. we'd introduce a new "autosleep" scale step between 0 and 1, eg. the dyno scale slider would be: 0 -> autosleep -> 1 -> 2+.

We would like this for Enterprise as well for our review, development and staging apps (so not only for Heroku Teams).

calculuschild commented 10 months ago

Just ran into this myself. I run a small open source app, and with only a couple of us working actively on the project, it can take quite a while to work through all of the proposed PRs, which means they hang around for often months at a time.

Eco dynos were great for this, but as I tried to move into a Team so the other person can help manage the site while I am going on vacation, suddenly our server costs skyrocketed 50x, not realizing Teams uses standard dynos instead of Eco for our 49 open PR review apps. Luckily we realized after just one day, but imagine if that had gone on for a full month. Free open source projects can't sustain that kind of surprise billing.

Please give us some way to use Eco dynos for review apps on small teams! And please make it abundantly clear to users when transferring ownership of a project from Personal to Teams that all Review Apps will suddenly be billed at a higher rate!