3 ms·

At the very smallest scale for a solo developer or a team of just a couple of people it can be a good option. Once the team grows to even 5 or 10 engineers, I'

by cactus2093 5y ago

At the very smallest scale for a solo developer or a team of just a couple of people it can be a good option. Once the team grows to even 5 or 10 engineers, I'm not a big fan. The model of encouraging anybody to do a git push to send their local copy of a branch to production is a little sketchy on even a small team. IMO you're better off having an automated build pipeline with CD by that point using something like gitlab or github actions, and putting your production environment into a proper VPC, i.e. generally starting to step up your engineering practices. You can still do these things with Heroku, but at that point you need to start kind of knowing what you're doing anyway and so you lose the main benefit of Heroku that it just magically works without needing to know anything about it. In my experience by that point you're fighting against Heroku more often than not and you're better off using something that is designed to be more flexible and give you more control like Kubernetes on GCP or AWS.

enahs-sf 5y ago
As a solo developer, running a small instance yourself and just SSH’ing in or writing a few simple scripts to deploy is probably more worthwhile. You have to deal with the “headache” of setup but at least you know what’s going on underneath the hood.
nightpool 5y ago
"The model of encouraging anybody to do a git push to send their local copy of a branch to production is a little sketchy on even a small team" Does anybody still do that for major apps these days? We've used a custom chatops bot based on Hubot for all of our deploys on Heroku for the past ~8 years, and they've recently released their own chatops solution that I've used for smaller apps and enjoyed. Using their new chatops bot is extremely turnkey—you can set it up to autodeploy from a Github branch or deploy manually, just by connecting a Github repo
bradgessler 5y ago
What’s annoying about Heroku and AWS is they made it an “either/or” situation that I don’t see a lot of people challenging. My ideal would be a service like Heroku that makes it easy to evolve. When the team is between 1-5 people iterating rapidly towards PMF, make ‘git push’ deploy. As the team grows and CI is needed, make it easy to decouple git from the deployment and support multiple envs. This is where Heroku stops. Finally when the app becomes larger and more complicated, it should be easy to spin up resources in AWS (or whatever cloud) behind a VPC. Migrating the heroku-like PaaS into this VPC should be easy.
- flybayer 5y ago
  We just launched Flightcontrol[1] last month which provides the DX of Heroku (arguably better actually), but deploys all the resources to your own AWS account. Git push to deploy fargate containers + automatic CDN + easy custom domains + auto https + multiple services per environment. Coming soon is databases, private workers, static sites, and multi service preview environments. We set up everything with best practices using VPCs, etc. We link directly to AWS services from our dashboard, but you don't have to know anything about devops. If any of you try it out, I'd love any feedback you have for us! [1] https://flightcontrol.dev https://flightcontrol.dev

enahs-sf 5y ago

As a solo developer, running a small instance yourself and just SSH’ing in or writing a few simple scripts to deploy is probably more worthwhile. You have to deal with the “headache” of setup but at least you know what’s going on underneath the hood.

nightpool 5y ago

"The model of encouraging anybody to do a git push to send their local copy of a branch to production is a little sketchy on even a small team" Does anybody still do that for major apps these days? We've used a custom chatops bot based on Hubot for all of our deploys on Heroku for the past ~8 years, and they've recently released their own chatops solution that I've used for smaller apps and enjoyed. Using their new chatops bot is extremely turnkey—you can set it up to autodeploy from a Github branch or deploy manually, just by connecting a Github repo

bradgessler 5y ago

What’s annoying about Heroku and AWS is they made it an “either/or” situation that I don’t see a lot of people challenging. My ideal would be a service like Heroku that makes it easy to evolve. When the team is between 1-5 people iterating rapidly towards PMF, make ‘git push’ deploy. As the team grows and CI is needed, make it easy to decouple git from the deployment and support multiple envs. This is where Heroku stops. Finally when the app becomes larger and more complicated, it should be easy to spin up resources in AWS (or whatever cloud) behind a VPC. Migrating the heroku-like PaaS into this VPC should be easy.

flybayer 5y ago
We just launched Flightcontrol[1] last month which provides the DX of Heroku (arguably better actually), but deploys all the resources to your own AWS account. Git push to deploy fargate containers + automatic CDN + easy custom domains + auto https + multiple services per environment. Coming soon is databases, private workers, static sites, and multi service preview environments. We set up everything with best practices using VPCs, etc. We link directly to AWS services from our dashboard, but you don't have to know anything about devops. If any of you try it out, I'd love any feedback you have for us! [1] https://flightcontrol.dev https://flightcontrol.dev