Hacker News new | past | comments | ask | show | jobs | submit login

Because an IaaS is not a PaaS, and people who were previously dependent on Heroku probably don’t have the DevOps skillset required to use an IaaS?

I know Elastic Beanstalk and Lightsail both exist; but they’re both much more complicated than `git push heroku master`. And that’s not even counting what you have to do/learn to be able to wire up a DB or Redis instance or Email deliverability on AWS.




I should just start a startup that converts heroku into an AWS instance then because its straightforward


I have various friends/acquaintances/prior coworkers running 8-9 figure digital/IT agencies premised on very similar workflows.

Straightforward to you may still be magic to most non-tech people. They will pay an insane premium to not have to worry about this type of stuff.


8-9 figures on webhosting/helping non technical people manage and deploy some app? Or you're saying those digital agencies would pay a premium to be an end user.


Cloud66 provides a Heroku-like experience on EC2 instances in your AWS account. (plus there are open source options, like Dokku)


When I had to work with Heroku, I found that it had many of its own specific eccentricities.

And to do the setup of a bare metal web service was not much more to know.

This is especially true looking at prebaked stuff like what digital ocean offers. You can use their Django image and the entire thing is ready to go.

Ultimately, docker and docker orchestrations are fairly standard devops skills at this point.

I think these paas solutions take devs who might otherwise bite the bullet and learn how to work with these in the wrong direction.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: