Live data from Hacker News

GitLab is now running on GCP

twitter.com

1–10 of 163 posts

Re: GitLab is now running on GCP

#5
GKE is fantastic to work with, we rolled with that on a nascent project in favour of Heroku and other PaaS. We had one or two rough spots but we’re not paying nearly as much as we would to have the entire thing managed by other parties, along with the accounting and awareness overhead that incurs. Kubernetes has a learning curve but it delivers an elegance too.

The ulterior motive is that understanding Kubernetes now has serious professional value in and of itself, so if the product fails your experience certainly doesn’t.

That said, I’m surprised Gitlab didn’t announce a new nav redesign at the same time ;)

Re: GitLab is now running on GCP

#6
post #5

GKE is fantastic to work with, we rolled with that on a nascent project in favour of Heroku and other PaaS. We had one or two rough spots but we’re not paying nearly as much as we would to have the entire thing managed by other parties, along with the accounting and awareness overhead that incurs. Kubernetes has a learning curve but it delivers an elegance too. The ulterior motive is that understanding Kubernetes now…

But the cost of Heroku on free, or nearly free tier, isn’t comparable to GKE. When I tried to launch a demo cluster it was basically launching numerous VMs just to support itself. I don’t know the monthly total, since I abandoned that idea pretty quick. But I imagine it’d be over $50/mo to run a tiny web app.

My point is that every offering has its place. Heroku is great for getting going.

Recently I’ve been experimenting with Dokku. I think it’s a totally viable alternative to Heroku. I do value my time, and understand the value of PaaS. But when Heroku starts charging insane amounts for Redis memory, it made me look for easy alternatives and Dokku fits the bill well.

Re: GitLab is now running on GCP

#7
post #4
post #2

Backstory: https://about.gitlab.com/2018/06/25/moving-to-gcp/

Real backstory: https://news.microsoft.com/2018/06/04/microsoft-to-acquire-g...

Why does this dumb story keep getting posted on every GitLab thread? GitLab started the move to GCP way, way before the acquisition from MS happened. They are not related.

Re: GitLab is now running on GCP

#8
post #6
post #5

GKE is fantastic to work with, we rolled with that on a nascent project in favour of Heroku and other PaaS. We had one or two rough spots but we’re not paying nearly as much as we would to have the entire thing managed by other parties, along with the accounting and awareness overhead that incurs. Kubernetes has a learning curve but it delivers an elegance too. The ulterior motive is that understanding Kubernetes now…

But the cost of Heroku on free, or nearly free tier, isn’t comparable to GKE. When I tried to launch a demo cluster it was basically launching numerous VMs just to support itself. I don’t know the monthly total, since I abandoned that idea pretty quick. But I imagine it’d be over $50/mo to run a tiny web app. My point is that every offering has its place. Heroku is great for getting going. Recently I’ve been experime…

You can have it both ways by leveraging the free / hobby tier of Heroku with bringing your own data store. Nothing binds you to their resource providers. Just add an environment variable for your own database or Redis provider.

Re: GitLab is now running on GCP

#9
post #4
post #2

Backstory: https://about.gitlab.com/2018/06/25/moving-to-gcp/

Real backstory: https://news.microsoft.com/2018/06/04/microsoft-to-acquire-g...

The GCP move was decided upon months before Microsoft acquired GitHub[1].

[1]: https://venturebeat.com/2018/04/06/why-and-how-gitlab-abando...

Post reply on HN