Earlier quoted context omitted.
Hey! Lee from Vercel here. Vercel isn't just for static sites – it also handles server-rendered applications, serverless functions, and hybrid frameworks (like Next.js). The current focus has been on an incredible front-end experience, but we're working to become a first-party integrator with your favorite backend solutions. For example, you can deploy a full-stack Next.js application with a PostgreSQL database in le…
Isn't serverless still just lambda..? Slow to boot, and subject to denial-of-wallet attacks. I do love vercel for static sites, and also think my blog with a minimal backend for comments is a good fit. But less sure how it'll hold up to even a single heroku dyno, which can do a lot of concurrent request at very low cost.
We are far from a better Heroku for production apps in a hyper cloud
271–275 of 275 posts
Re: We are far from a better Heroku for production apps in a hyper cloud
#272Earlier quoted context omitted.
> 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.
I do question the “kitchen sink” product strategy and whether it’s sustainable - Atlassian pulled it off by building a product line rather than an all-in-one.
Re: We are far from a better Heroku for production apps in a hyper cloud
#273There is already a better Heroku and it's Vercel (previously Zeit) https://vercel.com/ I believe Vercel is the spiritual successor of Heroku. I guess Heroku got bought by Salesforce and the founders/visionaries left. Heroku should have moved to bill per seconds/milliseconds based on AWS Lambda functions like Vercel did later.
Re: We are far from a better Heroku for production apps in a hyper cloud
#274Earlier quoted context omitted.
Heroku's pricing is also justified IMO, since if you're using Heroku you're most likely saving money on hiring an on-call infrastructure or ops team, and saving money on having your engineers switch focus from feature development to maintaining the system, or doing dev-ops work. You're paying Heroku to do the operational stuff for you so you can spend more time building your product. That's a price well worth paying…
> even then I don't think the default next step is going full-blown cloud and K8S What would you suggest as a 'next step' after heroku?
Re: We are far from a better Heroku for production apps in a hyper cloud
#275Earlier quoted context omitted.
As long as it is faster than gitlab itself, sure. Every time I go to the hosted gitlab, I cringe. I like the product but the whole thing is sooo slow. First, 5 seconds wasted to "check if my browser supports gitlab", then the lag on every click. Hopefully your heroku will have a better experience than your gitlab.
Isn't that "5 seconds" a cloudflare thing?