181–190 of 230 posts
Earlier quoted context omitted.
correct. RDS does not even let you do a true, vanilla postgres backup to s3. the lock-in is complete
You can easily use pg_dump to do a "vanilla" backup to s3. Its a managed db service but if you wanted to run your own you can extract your data and move to a new db. The lock is not "complete" you are acting like you can't even extract your data.
Earlier quoted context omitted.
disclaimer: former Heroku person here too Some examples of the things I've missed around developer experience for a database, that Craig and the team made possible at Heroku Postgres, include: - fork: ever had one of those "why does this bug only exist in production?" problems? It was so trivial to fork the DB and run your tests/hypothesis/whatever without the risk of actually impacting production. Same thing for _re…
> - fork: ever had one of those "why does this bug only exist in production?" problems? It was so trivial to fork the DB and run your tests/hypothesis/whatever without the risk of actually impacting production. Same thing for _really_ testing a migration script or load test. This sounds great! How does it work though? Is it using some special postgres feature or btrfs snapshots or something else completely?
- restore from the latest snapshot (there was one whether you’d configured a custom backup schedule or not)
- replay the write ahead log over the top to catch the restore up to the point in time you asked for/when you ran the command. At least some part of this process leveraged WAL-E, which was a tool largely developed by Heroku employees and open sourced.
This was a decade or more ago though. The state of the art of postgres has moved on and I assume the team would tackle it differently if they were doing it today.
Earlier quoted context omitted.
> we haven't been able to deploy for over two weeks What is stopping you? Are you unable to type `git push heroku master`?
I think you're underestimating the complexity of our codebase. Aside from the usual blockers, we have hundreds of repos (our Staging feature for Enterprise allows customers to deploy our code on their own cadence) all tied together using pipelines. We have our own custom release management software, which now doesn't work. Different repos have to go out at the same time so things don't break. Plus, we extensively use…
Edit: ah I see you're looking into moving already
We're big Heroku customers; despite that, I largely agree with the points in this article and there's a voice in the back of my head asking every few months "is this worth it?" Whenever I research the new crop of Heroku clones (the one being hawked here, and others) the pitch is always "it's just like Heroku but you can run it in your own cloud". It's mind-boggling to me that none of the clones understands that I DON…
People somehow magically forget that then they will need to run their own servers to host k8s and then deal with k8s and then deal with their app deployment.
If I can deploy app just like on Heroku and not have a server and not have to deal with orchestrator that is winning deal for me. Other way I will stay with my VPS setup and install apps directly on these.
As someone that was there at Heroku after the acquisition, I don't think you can state that since the acquisition it's been consistently downhill. There isn't much debate that things have stagnated in the last 5-7 years which is a longer story on why probably. Some examples of innovation that happened and were launched after the acquisition: buildpacks (at the time of acquisition Heroku was still Ruby only), Heroku P…
I think the most interesting part of this is the PaaS disaggregation. Heroku built an exceptionally good Postgres service. They could not have done that with multiple DBs. Even their redis is pretty meh. People like us (Fly.io) will end up either building very mediocre DB offerings or collaborating with DB companies (like yours: https://www.crunchydata.com/products/crunchy-bridge/ ) to ship stuff that's substantially…
My current strategy is to use Heroku to test waters, If the validation is successful then migrate to fly.io.
Very widely used by enterprise, but also free and open-source.
Alternatives to Heroku besides Porter?
Worth trying it out yourself, they’re dirt cheap atm.
There are some really strong downsides (especially after the last 2 weeks) but as a dev team of 1 (mostly) it's been a life saver, and that's enough to overrule all the other downsides.
Having said that, we've suffered our own issues, with cost, latency (we're in AU) and scaling being the main ones.
We're building a new product that we're betting very heavily on and it's all on AWS serverless. I wouldn't choose Heroku again.
I think it was worth it 5 years ago, but as time goes on it becomes harder to justify.
When Heroku was incorporated by Salesforce there was no consumer facing capabilities in SF: everything was for business/sales users so Heroku was attractive to build public facing assets seamlessly connected to SF data (hence Heroku Connect). But then SF started incoporating other consumer facing featuers: Communities, Commerce (Demandware), heck they even have their own CMS now. One can predict they will push lowcode/citizen development beyond Force.com. Where does that leave Heroku? What does it bring to the table now for Salesforce?
A good article, except for one big thing: this is not an end user, rather a direct competitor. Public articles that criticize competitors always run me the wrong way. I haven't used Heroku in a few years, but it has served (using the Hobby plan) as a really low cost way to host web apps. I have been reading through the comments on alternative providers, and even though I haven't used it, GCP's Cloud Deploy looks inte…
Check Netlify Or Vercel Best scaling in their free plans Heroku hobby is a joke in comparison and hasnt been updated in a decade while all their addons have gotten less and less featured while costing more and more I host all my static assets on IPFS which practically nullifies the bandwidth limits of Netlify