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

Weaveworks is shutting down

linkedin.com

Post reply on HN
Print view View original

31–40 of 266 posts

Re: Weaveworks is shutting down

#31

Post by mfer »

mad_vill wrote: post #13

I feel like the next generation of this type of company is smaller consultancies that have awesome developers that build customer tooling on the side. But the main revenue driver is consultancy. Also it really feels like all the air has been let out of the docker/kubernetes/cloud-native balloon that was so popular in the late 2010s.

VC funded and looking for growth opportunities is far different than building a long term sustainable business. The carrot in the business model leads business decisions in very different directions and your setup is different to meet them.

Are there opportunities for VC funded with growth expectations in this kind of business?

Re: Weaveworks is shutting down

#33

Post by break_the_bank »

kwerk wrote: post #20
break_the_bank wrote: post #17

> The company was turning over double digit revenue and had more than doubled the number of new product logos in 2023. From the LinkedIn post. Does this mean $100 MRR / ARR ?

I think they meant to say "double digit revenue growth "

That makes more sense! Thank you.

Re: Weaveworks is shutting down

#34

Post by xenophonf »

marcinzm wrote: post #21
mad_vill wrote: post #13

I feel like the next generation of this type of company is smaller consultancies that have awesome developers that build customer tooling on the side. But the main revenue driver is consultancy. Also it really feels like all the air has been let out of the docker/kubernetes/cloud-native balloon that was so popular in the late 2010s.

> Also it really feels like all the air has been let out of the docker/kubernetes/cloud-native balloon that was so popular in the late 2010s. Not really, the space has simply grown faster than these companies could keep up with and were left behind. I can code up a CICD pipeline that does per-PR namespace isolated deploys of an app stack on EKS using Github actions in well under a week. With docker compose for local…

> a CICD pipeline that does per-PR namespace isolated deploys of an app stack on EKS using Github actions... [with] docker compose for local testing

Please teach me, oh wise prince!

Re: Weaveworks is shutting down

#35

Post by dilyevsky »

whalesalad wrote: post #26
menthe wrote: post #25

Earlier quoted context omitted.

Kinda surprised anyone would still using WeaveNet as a CNI.. it was a bit of a dumpster fire: https://blog.quentin-machu.fr/2020/08/07/our-breakup-with-we...

what is the idiomatic approach these days?

Cillium is probably the most rock solid option these days. They are still pumping out releases even though they had been recently sold to cisco

Re: Weaveworks is shutting down

#36

Post by swozey »

marcinzm wrote: post #21
mad_vill wrote: post #13

I feel like the next generation of this type of company is smaller consultancies that have awesome developers that build customer tooling on the side. But the main revenue driver is consultancy. Also it really feels like all the air has been let out of the docker/kubernetes/cloud-native balloon that was so popular in the late 2010s.

> Also it really feels like all the air has been let out of the docker/kubernetes/cloud-native balloon that was so popular in the late 2010s. Not really, the space has simply grown faster than these companies could keep up with and were left behind. I can code up a CICD pipeline that does per-PR namespace isolated deploys of an app stack on EKS using Github actions in well under a week. With docker compose for local…

Hell, we do it once in terraform/pulumi/cdk and then it takes 10 minutes to tweak some variables and switch aws accounts and bam

Our devs/SRE put up apps and clusters in minutes (aside from the terrible alb/ecs/eks/etc deployment times).

Re: Weaveworks is shutting down

#37

Post by FourierEnvy »

marcinzm wrote: post #21
mad_vill wrote: post #13

I feel like the next generation of this type of company is smaller consultancies that have awesome developers that build customer tooling on the side. But the main revenue driver is consultancy. Also it really feels like all the air has been let out of the docker/kubernetes/cloud-native balloon that was so popular in the late 2010s.

> Also it really feels like all the air has been let out of the docker/kubernetes/cloud-native balloon that was so popular in the late 2010s. Not really, the space has simply grown faster than these companies could keep up with and were left behind. I can code up a CICD pipeline that does per-PR namespace isolated deploys of an app stack on EKS using Github actions in well under a week. With docker compose for local…

Yeah I literally did this last week for a new in house AI assistant for my company. Just swap out Jenkins for GH actions (sadly). So... can confirm.

Re: Weaveworks is shutting down

#38

Post by swozey »

mad_vill wrote: post #13

I feel like the next generation of this type of company is smaller consultancies that have awesome developers that build customer tooling on the side. But the main revenue driver is consultancy. Also it really feels like all the air has been let out of the docker/kubernetes/cloud-native balloon that was so popular in the late 2010s.

> Also it really feels like all the air has been let out of the docker/kubernetes/cloud-native balloon that was so popular in the late 2010s.

Kubernetes is just boring now. It's stable, the people who need to know it probably know it. I started working and contributing to k8s in 2015 back in version 1.1. 7 years of the same technology. I haven't even used it in 2-3 years (1.18) and I know I can hop over to it and do exactly what I used to do with some CRD flare.

All of the contributors should be proud of what they've built, that's the goal in the end, stability to where it's an afterthought.

Re: Weaveworks is shutting down

#39

Post by upupupandaway »

marcinzm wrote: post #21
mad_vill wrote: post #13

I feel like the next generation of this type of company is smaller consultancies that have awesome developers that build customer tooling on the side. But the main revenue driver is consultancy. Also it really feels like all the air has been let out of the docker/kubernetes/cloud-native balloon that was so popular in the late 2010s.

> Also it really feels like all the air has been let out of the docker/kubernetes/cloud-native balloon that was so popular in the late 2010s. Not really, the space has simply grown faster than these companies could keep up with and were left behind. I can code up a CICD pipeline that does per-PR namespace isolated deploys of an app stack on EKS using Github actions in well under a week. With docker compose for local…

How does your pipeline work with an app that requires many other services to work?

Re: Weaveworks is shutting down

#40

Post by FourierEnvy »

swozey wrote: post #36
marcinzm wrote: post #21

Earlier quoted context omitted.

> Also it really feels like all the air has been let out of the docker/kubernetes/cloud-native balloon that was so popular in the late 2010s. Not really, the space has simply grown faster than these companies could keep up with and were left behind. I can code up a CICD pipeline that does per-PR namespace isolated deploys of an app stack on EKS using Github actions in well under a week. With docker compose for local…

Hell, we do it once in terraform/pulumi/cdk and then it takes 10 minutes to tweak some variables and switch aws accounts and bam Our devs/SRE put up apps and clusters in minutes (aside from the terrible alb/ecs/eks/etc deployment times).

Yeah this is nice if you have large teams and repeatable projects. Smaller companies have much more ad-hoc requests. I stood up an entirely new type of project end-to-end from a docker compose into our cluster. Re-used alot of code base but it was still a bit of work. Much less than it used to be though.
Post reply on HN