Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

We are far from a better Heroku for production apps in a hyper cloud

about.gitlab.com

Post reply on HN
Print view View original

131–140 of 275 posts

Re: We are far from a better Heroku for production apps in a hyper cloud

#131

Post by ksec »

jelling wrote: post #115
dubcanada wrote: post #10

People 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…

AWS may be the gold standard for hosting but I still recommended most startups start with Heroku for their hosting, especially since they add the code pipelines. The amount of VC dollars I have seen wasted on re-inventing the wheel of hosting/devops is a textbook case of premature optimization.

Amazon really should have bought Heroku instead of Salesforces. I continue to wonder why Salesforce bought it in the first place. And if they are willing to unload it.

Re: We are far from a better Heroku for production apps in a hyper cloud

#132

Post by funnygitlab »

sytse wrote: post #19
rattray wrote: post #12

Earlier quoted context omitted.

This was a great comment until the mean-spirited last word.

I’ll ignore the last word. The article doesn’t do a great job of showing it, but the 5 minute production app makes it easier to setup stateful services on the hyper clouds. And it does spin up a new environment for every merge request.

> I’ll ignore the last word.

I dont think you should. Being the CEO of the company which published this blog, the last thing you should do is ignore a genuine review of what quality that blog post is.

Re: We are far from a better Heroku for production apps in a hyper cloud

#133

Post by detaro »

ksec wrote: post #131
jelling wrote: post #115

Earlier quoted context omitted.

AWS may be the gold standard for hosting but I still recommended most startups start with Heroku for their hosting, especially since they add the code pipelines. The amount of VC dollars I have seen wasted on re-inventing the wheel of hosting/devops is a textbook case of premature optimization.

Amazon really should have bought Heroku instead of Salesforces. I continue to wonder why Salesforce bought it in the first place. And if they are willing to unload it.

Heroku not being AWS might be a feature. I'm not sure if AWS wouldn't try and integrate them and "break" something in the process. Whereas now, they still get money from it (Heroku runs on AWS) and can offer their own "alternatives" as part of the larger AWS offering.

Re: We are far from a better Heroku for production apps in a hyper cloud

#134

Post by boleary-gl »

squaresmile wrote: post #129
dnsmichi wrote: post #100

Author 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.

I like that title a lot - it is a more concise statement.

Re: We are far from a better Heroku for production apps in a hyper cloud

#135

Post by ksec »

detaro wrote: post #133
ksec wrote: post #131

Earlier quoted context omitted.

Amazon really should have bought Heroku instead of Salesforces. I continue to wonder why Salesforce bought it in the first place. And if they are willing to unload it.

Heroku not being AWS might be a feature. I'm not sure if AWS wouldn't try and integrate them and "break" something in the process. Whereas now, they still get money from it (Heroku runs on AWS) and can offer their own "alternatives" as part of the larger AWS offering.

The idea would be to allow Heroku working independently while offering their solution at literally AWS cost (without all the discount), or even AWS Graviton2 cost.

This would pretty much directly compete with Linode and DO on a value proposition. And a lock in to AWS ecosystem.

Re: We are far from a better Heroku for production apps in a hyper cloud

#136

Post by funnygitlab »

So this looks like signs that after getting a boat load of money from their VCs, promising to be a "better github", the VCs have realized that they have been played. So it looks like the gitlab team has been asked to pursue other avenues to widen their horizons and get some returns for the VC investments. So they go from "we will be better github" to "we will be better heroku".

How will they do that? "Productized apps for hyperscale cloud". What does that mean? It's a bunch of buzz words our marketing and sales team invented.

Re: We are far from a better Heroku for production apps in a hyper cloud

#137

Post by ctas »

rcarmo wrote: post #83
dubcanada wrote: post #10

People 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…

Yep. Heroku's workflow is why I created Piku ( https://github.com/piku/piku ). I wanted something dead easy for deployments and updates when iterating.

Interesting. On Dokku installing postgres and redis takes just two commands. How would the equivalent look on piku?

Re: We are far from a better Heroku for production apps in a hyper cloud

#139

Post by john_cogs »

emayljames wrote: post #76
arthurcolle wrote: post #70

Earlier quoted context omitted.

I would definitely caution you + the author of this post to tone down the rhetoric. Heroku has earned a tremendous amount of goodwill by being... basically fucking awesome and enabling tremendous amounts of productivity without having to screw around with infinite configuration settings. Just earn your own goodwill on your own merits, not by denigrating an extremely competent "competitor"

Yeah, a basic rule is don't bad mouth competition, it will always reflect on you and not your competition.

Thanks for the feedback. I agree.

Re: We are far from a better Heroku for production apps in a hyper cloud

#140

Post by [deleted] »

jack_riminton wrote: post #66
Trasmatta wrote: post #61

Earlier quoted context omitted.

You can do the majority of Heroku interactions on the CLI if you prefer.

I know, and I do The quote was from the blog. Making it seem like doing things off the CLI was a plus point Right now I have a git alias that does everything, including pushing to my heroku master, in one command. Why would I want to go off the CLI?

[deleted]
Post reply on HN