Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Heroku Postgres] [Grow on demand]: Pay for usage as it scales to meet your needs #57

Open
2 tasks done
afawcett opened this issue Sep 13, 2022 · 2 comments
Open
2 tasks done
Assignees

Comments

@afawcett
Copy link

afawcett commented Sep 13, 2022

Required Terms

What service(s) is this request for?

Heroku Postgres

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

Elastic Postgres, automatically expands resources and cost in alignment with customer demand. Simplifies data growth by reacting to observed conditions, and automatically upgrading resources as the customers business demands it. Customers only pay for what they are using. No need to plan ahead for new data tiers. All the same values of Heroku Postgres but with no data restrictions and jarring upgrades to move to new tiers.

@afawcett
Copy link
Author

Here is a slide we shared at Dreamforce recently.

Image

@karlbecker
Copy link

karlbecker commented Oct 27, 2022

This would be really nice to have, especially since some other Postgres hosts let us do this, too. Currently on Heroku Postgres, if we need more than 1.5TB of disk space, but don't need any additional CPU or RAM, we must pay at least $1500/month extra per database instance just to have 1.6TB to 2TB of disk space (the difference between a Standard 6 and Standard 7). If we have multiple read-only followers, we need to spend $1500 extra for each follower.

Considering hard drive space on AWS is pretty cheap per GB (much less than $1500/month for 500GB), this is an important feature to us.

Also, the slide says future - any estimate, even a rough one, on when this might be available to Heroku customers, either Enterprise or otherwise? Thanks!

Edit: I see this is in the "Researching" state currently, so I take that to mean there's likely no chance of this being shipped in general availability to Heroku in 2023. Is that a reasonable assumption?

I also think this is pretty much a duplicate of #60

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: 📋 Researching
Development

No branches or pull requests

5 participants