Read the article. Came here for the comment thread. Was not disappointed.
We are far from a better Heroku for production apps in a hyper cloud
121–130 of 275 posts
Re: We are far from a better Heroku for production apps in a hyper cloud
#122Earlier quoted context omitted.
Can you explain what you mean by ‘for production apps’? Because some people are definitely using Heroku in production.
Production apps in a hyper scale cloud
What do you think where Heroku apps run? Why would anyone truly caring about hyperscale trust Gitlab to handle that?
Re: We are far from a better Heroku for production apps in a hyper cloud
#123using heroku, we don't have to worry about infrastructure (much). having terraform in the pipeline kind of defeats that.
Re: We are far from a better Heroku for production apps in a hyper cloud
#124Earlier quoted context omitted.
> Everything? I thought it was supposed to be Git hosting, but I'm not even sure anymore. They're losing to GitHub. While they advertise that they have 2/3 of the self-hosted git server market share, they just barely have a double digit share of the total VCS market, which is where the real enterprise money and value is. I don't have figures on hand, but I'd guess they have a single digit percentage of actual enterpr…
> They're losing to GitHub In my experience their approach to pipelines and CI is a winner. In that regard GitHub seems to be playing catchup and the "checks" feel like second class citizens in GitHub while it feels really cohesive in GitLab.
Sure. I wouldn't be surprised if they have better features along specific dimensions. I'm talking about monetizable market share and revenue.
Re: We are far from a better Heroku for production apps in a hyper cloud
#125This was very cringey. A super contrived demo and bashing Heroku through a Twitter reference. Reads like someone is drunk/high and wanted to shitpost about a competitor. I would be appalled by this if I were GitLab's PR department!
It's written by a developer with a disclaimer that it's "unfiltered". I think it's part of their PR strategy to sound authentic and not salesy. Seems to mostly work for them.
Re: We are far from a better Heroku for production apps in a hyper cloud
#126Re: We are far from a better Heroku for production apps in a hyper cloud
#127> The Git URL unfortunately does not provide access. Sorry to say but not having a git web UI doesn't mean you can't access it. The very next command you push to it via `git push heroku main`, meaning you have full access to it, including the ability to force push to it.
Yeah, I think it would have been better to differentiate in the article based on setting up state. It takes a while to configure a persistent database, redis, and storage on Heroku. That is what we’re trying to make easier, as well as hosting it on a hyper cloud. See https://gitlab.com/gitlab-org/5-minute-production-app/deploy...
I have been following these gitlab promotion threads here at HN and I dont usually comment, but I had to create this account after reading this post. It looks really bad and incompetent when a CEO of the company makes a statement like this. Have you ever used Heroku? On what basis are you allowing people to bash that product on your website? Do you consider Heroku your competitor? On what technical abilities of Gitlab do you think you have reached a place where you consider them your competitor? Some random meaningless doc someone put together to show how you will do better?
Re: We are far from a better Heroku for production apps in a hyper cloud
#128People 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…
I am not a Heroku user so cannot assess how this compares to their offering but as someone who spends ~4 hours a day looking at Terraform and the AWS console this does not look "production" quality at all.
* The web app is deployed to a single AWS EC2 instance which cannot be scaled horizontally.
* The web server is deployed from an AMI filter, when a new AMI matches this filter there will be downtime to redeploy the instance entirely.
* There does not seem to be any considerations for patching the web server.
* Everything shares a single security group. Although this is probably fine because you are using managed services for redis and postgres its still weird to allow port 443/22 from anywhere on your database.
I'd be happy to be proven wrong on these points.
There also seems to be quite a bit of assumed knowledge about AWS and Terraform. You mention the free tier a lot, but that only applies for the first year since your AWS sign up. After the free tier is up this infra is going to cost $40+ per month.
Re: We are far from a better Heroku for production apps in a hyper cloud
#129Author here. This post doesn't live up to its title, I'm sorry about that. The title should have been 'We are building a better Heroku FOR PRODUCTION APPS' (we'll add the 'for production apps' to the title) It should have emphasized the _building_ part, we're just starting. The current 5 minute production app doesn't hold a candle to Heroku at the moment. It should have made it clear the goals is to improve the speed…
Yeah, I agree with the comments that the "for production apps" distinction is a bit weird. I would title it "We are building a Heroku-like experience for big cloud providers".
I can see the point of a service like this and the comparison is cool but there's no need to complain about Heroku, especially when the Gitlab services are not 100% equivalent. If you come for the champ, you'd better not miss and all that.
Re: We are far from a better Heroku for production apps in a hyper cloud
#130> A typical web app requires a database, storage or caching backend, which can get complicated to run with Heroku. Plainly wrong. Easiest thing ever to spin a pg instance for free and have it immediately available for your app to use. Better Heroku? Does it let you use a pipeline of dev, staging and prod? Does it auto create new copies of your app (db and other services included!) every time you issue a pull request?…
This was a great comment until the mean-spirited last word.
It's not a mean spirited word. Gitlab and their army of users who post here at HN and bash their "competitors" have earned this. See their past threads where they have done a similar thing against github.