[littlecranky67]

Hearing a lot about monolith vs. microservices, can someone shed some light how "pluggable/plug-in driven monoliths" fit in? To Quote Martin Fowler on monoliths:

> Change cycles are tied together - a change made to a small part of the application, requires the entire monolith to be rebuilt and deployed.

But this is not true. I worked at some C# "monolith" ~2010ish, and we used MEF framework to build pluggable .dll files that you could just "drop" into the deployment folder. As long as you stuck to the same interfaces (through a shared interfaces project) you could build and ship individual parts of the application in separate teams. Even exceptions could not harm the full system (when they were properly caught in the host) - and segfaults shouldn't happen in a managed system (but yes, they did, mostly through P/Invokes).

I always liked the good old "Winamp model" where you would just drop some dlls and got new visualization plugins enabled - each more different than the other.