I think the title is a bit confusing. "We are building a better Heroku" implies some sort of announcement that Gitlab is adding a new service to their offerings, and that's what I expected when I clicked. This is more like a tutorial for how to make a deploy pipeline using Gitlab.
We are far from a better Heroku for production apps in a hyper cloud
41–50 of 275 posts
Re: We are far from a better Heroku for production apps in a hyper cloud
#42Has GitLab already finished building a better GitHub before they waste time in a better Heroku when in fact nobody else thinks that we need a better Heroku?
Last time I checked GitLab was still significantly slower than GitHub.
Re: We are far from a better Heroku for production apps in a hyper cloud
#43Honestly, this article presents a fairly ridiculous comparison. You could bump deploy times on Heroku to 20 minutes and I would still use it without a second thought. At best, I'll complain a little louder.
Here's step 1 from the article: The documentation says to create a new AWS IAM role with credentials for automation.
At this point, you've already failed. You are forcing more complexity on me than I have to care about when using Heroku. And the underlying complexity is worse. You need to be familiar with Gitlab's CI/CD pipelines. Your included YAML file hides all the complexity and uses all your magic variables: https://gitlab.com/gitlab-org/5-minute-production-app/deploy...
What happens when something breaks?
Quite literally, the only downside of Heroku is the pricing. Even that, I question for smaller teams where operational overhead can get way worse. I have yet to come across anything in the ballpark.
Anyway, this may still be a decent setup for deploying an app to AWS perhaps, but comparing to Heroku in the title is way off base.
Re: We are far from a better Heroku for production apps in a hyper cloud
#44These the same people who Jonny drop tables themselves?
https://twitter.com/gitlabstatus/status/826591961444384768
Re: We are far from a better Heroku for production apps in a hyper cloud
#45> Ended up in a Heroku blackbox for your stateful web app? GitLab introduces a better Heroku integrated into your DevSecOps workflow: The 5 minute production app.
Are we sure this wasn't written by some sort of new AI bot GitLab is employing? So many keywords stuffed in those opening lines.
The comparison in the article is incredibly naive, IMO; they are not being a better Heroku, this is just demonstrating something you can do if you already have good knowledge of three complex tools: AWS, Terraform, and GitLab Pipelines.
Re: We are far from a better Heroku for production apps in a hyper cloud
#46People do not use Heroku because it takes 5 minutes to spin up a box. They use it because it's super easy. Click a button, bam deployed. Want to add a database, click what database you want, bam you got a database, environment variables set and a GUI (depending on what you pick). Want to scale up? Click a button, you're now scaled up. Want a entire review system with staging links and everything? Setup the review pro…
Totally agree. The ease was the reason for us as well (although now running Cloud 66).
This post seems a bit disingenuous. Gitlap + Terraform + AWS != Heroku.
Re: We are far from a better Heroku for production apps in a hyper cloud
#47[deleted]
Re: We are far from a better Heroku for production apps in a hyper cloud
#48This was a confusing read. I guess GitLab has a hosting service, or does it? Or was this a demo of terraform?
More a demo of how GitLab pipelines and terraform work together. In this case the app was deployed to AWS.
but thats not even in the same ballpark as heroku or is it? people using heroku dont want to have anything to do with terraform
Re: We are far from a better Heroku for production apps in a hyper cloud
#49Earlier quoted context omitted.
I agree Heroku has the perfect dev environment, not much to improve there. We’re trying to make the perfect production environment. Most people end up hosting at a hyper cloud (edit: like AWS). We’re trying to make the app on a hyper cloud in production as easy as Heroku is in development. We’re still building that, it is t done by any means. And the article doesn’t do a good job of showing what we are trying to make…
but isnt that what AWS does with elastic beanstalk? elastic beanstalk always seemed to me as a "heroku with more dials"
I think that lots of the clouds will have their own offering, but having an open source based offering across clouds is what we're going for.
Also it's very early stages - but the goal would to be better than Beanstalk
Re: We are far from a better Heroku for production apps in a hyper cloud
#50People do not use Heroku because it takes 5 minutes to spin up a box. They use it because it's super easy. Click a button, bam deployed. Want to add a database, click what database you want, bam you got a database, environment variables set and a GUI (depending on what you pick). Want to scale up? Click a button, you're now scaled up. Want a entire review system with staging links and everything? Setup the review pro…
I agree Heroku has the perfect dev environment, not much to improve there. We’re trying to make the perfect production environment. Most people end up hosting at a hyper cloud (edit: like AWS). We’re trying to make the app on a hyper cloud in production as easy as Heroku is in development. We’re still building that, it is t done by any means. And the article doesn’t do a good job of showing what we are trying to make…
It would be helpful if the post was a bit clearer on that.
FWIW, I've used Heroku as a production environment at multiple jobs. It works great there as well. The primary issue in my experience is cost. If you need to serve a lot of traffic, Heroku gets very expensive very fast. But it's still easy to use.
That cost can be offset by the fact that you may not need to hire a dedicated devops engineer right away, and your other developers spend much less time dealing with server setup and debugging.