News for hackers. Stuff that matters.
Re:Goodbye Microservices: From 100s of problem children to 1... by apeace on Tuesday July 10, 2018 @01:59PM (#17500586)
My understanding is that OpenBSD is constructed this way, and I have also heard that their code is well-organized and easy to follow.

There is the "base" system which is the OS itself and common packages (all the ones you mentioned), then there is the "ports" repo which contains many open-source applications with patches to make them work with OpenBSD.

Here is a Github mirror of their repos: https://github.com/openbsd

I think OpenBSD has reaped many of the same advantages described by Segment with their monorepo approach, such as easily being able to add pledge[1] to many ports relatively quickly.

https://www.slideshare.net/GiovanniBechis/pledge-in-openbsd

Re:Goodbye Microservices: From 100s of problem children to 1... by fastball on Tuesday July 10, 2018 @02:07PM (#17500668)
"packages" and "ports" are both collections of "microservices" in your analogy, so you can't really assert the whole thing is a monolith.
Re:Goodbye Microservices: From 100s of problem children to 1... by lmm on Wednesday July 11, 2018 @06:55AM (#17505922)
The whole thing is released and deployed together, which is the usual distinction between microservices and not. I don't think anyone's advocating not using modules and folders to structure your code in your repository (certainly I hope not), but a single deployment artifact makes life a lot easier.