There's certainly a spectrum, but you can have huge clusters of even the most monolithic monolith.

The real semantic fun begins when you have monolithic codebase/deployments that could do everything, but each instance gets assigned a specialized role it serves to its peers _ (I think I've seen someonevdescribing that approach somewhere). I'd consider that micro if there are more than a handful of "roles", perhaps with some qualifier, but it would hopefully be easy to agree than no description is entirely wrong.

I’ve used this approach before, I wonder if there is a name for it ?

I haven't, but if I had and if I was trying to place it in the conference circuit, I'd call it morphoservice.

(and the actual me who has never reached beyond consumer side in conferences sure hopes that conferences would resist unless a less ridiculous name was found)

we would call it different "installations"

It's micro if it is so small that you question why this wasn't done as a library call in the same process.

It’s micro if it pulls <1gig of dependencies </s>

I have seen 5 table micro services. A solo backend developer had created "3 micro services" and as I joined the team, their argument was that we're doubled in strength so there were a series of architectural meetings to split everything nicely into 5 different services.

Hello world in NodeJS?

* clones hello_world repo

cd hello_world

npm install

* watches text scroll for five hours