News for hackers. Stuff that matters.

A comment on We Halved Go Monorepo CI Build Time. Parent comment

Re:We Halved Go Monorepo CI Build Time by steve_adams_86 on Sunday June 26, 2022 @10:35AM (#31884388)
I don’t understand how it’s possible to have close to 10,000 services. I worked on a project with 17 and found that to be very awkward at times (local development with k8s didn’t seem to be a solved problem, and we depended heavily on complex tests and blue/green deploys to be sure changes actually worked in production). But nearly 10,000 is insane.

How do you orchestrate that? I guess this is the kind of situation where you really do need container orchestration.

[ Parent | on HN ]
Re:We Halved Go Monorepo CI Build Time by schrodinger on Sunday June 26, 2022 @11:18AM (#31884777)
It's really easy to innocently slip into a culture of "new project? new service!" and at Uber's scale, that could easily hit 10k.
[ Parent | on HN ]
Re:We Halved Go Monorepo CI Build Time by steve_adams_86 on Monday June 27, 2022 @01:06AM (#31890772)
Yeah, I’m starting to realize my experience in software is even smaller scale than I thought.
[ Parent | on HN ]
Re:We Halved Go Monorepo CI Build Time by tootie on Sunday June 26, 2022 @01:23PM (#31885865)
Repos aren't one-to-one with running services. Lots of these could easily be bundled as modules to be included at build-time. A lot of them could also just be API services that provide a contract via REST or whatever. If you have enough internal users, you just have to maintain an SLA comparable to a public API.
[ Parent | on HN ]