Ask HN: Do people still use Heroku and the like?
With Docker-based deployments being the current hotness, you don't really read about services that do source-based deployments as much these days. Are they being truly supplanted, or are they still going steady just outside of the limelight?
Edit:
Did some research and found this good comparison: https://rubygarage.org/blog/heroku-vs-amazon-web-services. Looks like the technical terms are "Infrastructure as a Service" vs "Platform as a Service", where the latter is Heroku's main product.
Still interested in people's anecdotes, though!
(
13 comments
| 14 points
| on HN
)
In fact, I was using Digital Ocean for our company and in process of transferring everything to Heroku. It's been such a breath of fresh air/load off of my shoulders.
As the sole developer, I don't need to worry about my server going down and worrying about the database (although DO introduced managed databases recently). Heroku is perfect for our needs -- lots of scheduled one-off scripts and a rough API.
Have been looking at beanstalk but no. Now its between app engine and heroku. Question on heroku: It feels a bit weird they not support hardware 2fa, doesn't it?
Do you have any other insight to give me on your transition?
I looked into app engine a few years ago, but it felt more restrictive at the time.
Specifically I use dokku on a DO droplet. It does mean I have to manage the server myself which Heroku removes from the user, but again for a small company it’s just one server so it’s maybe an hour or two a month I spend on server admin. But my monthly cost for 15 projects running 24/7 is $10, compared to $100+ on Heroku. It’s not a huge difference if you’re funded or have a very profitable business, but my margins are thinner than I could afford with Heroku.
You can let Heroku build your image during the deployment phase by simply having a `Dockerfile` in your repository [1].
Or, you can build the image yourself on your CI service and push it to Heroku's registry and then trigger a release. This last option is useful if you want to run tests against the exact image that is going to be deployed without having to rebuilt it [2].
[1] https://blog.heroku.com/build-docker-images-heroku-yml [2] https://devcenter.heroku.com/articles/container-registry-and...
Maybe not the most wiz bang / get the attention more complex deployments have, but I suspect it is heavily used.