3 ms·
> Fact 3: No, it's not a myth, systemd is truly a huge monolith > In his blog post "The Biggest Myths", from January 2013, Lennart Poettering says: “A package
by xref 5y ago
> Fact 3: No, it's not a myth, systemd is truly a huge monolith
> In his blog post "The Biggest Myths", from January 2013, Lennart Poettering says: “A package involving 69 individual binaries can hardly be called monolithic.”
> The fact is however, that many of these so-called individual binaries has functionality that simply will not work without other systemd components.
Hmm I don’t agree that services relying on each other’s functionality means they’re a “monolith”. That sounds like a very different definition of monolith/microservice than I’m familiar with.
- akagusu 5y agoSystemd binaries are not a monolithic system but they are so tightly coupled that they are almost like a monolith. There is no api spec so you cannot swap any component exactly like a monolith, and this is why people call systemd a monolith and this is one of many reason a lot of people dislike systemd, because it's a non swappable batteries included app.
- zxzax 5y agoThat still doesn't make it monolithic. It's not exactly rare for an open source project to have no API spec. If you want to replace a part you just look at the code and then implement that API. If you ask me a lot of systemd is actually pretty easy to swap if you're interested, most is separated out into clean d-bus APIs.