Naming of the Service vs. Library pattern

While discussing some improvements to the Service vs. Library pattern (details in #353), @robtuley and I spoke about the naming of the pattern. Would a different name make it easier for the readers to understand the pattern?

Repeating some info from the PR below.

From me (@spier):

If you were to name this pattern, how would you call it?
I am asking because the pattern describes an approach that I might call "Library over Service" or "Separate Service Deployments" or "InnerSource with separate deployments".
I don't see the pattern really describing a comparison of InnerSource projects in both release approaches (Library + Service) but rather only focusing on the Library approach.

From @robtuley:

I also find the pattern name confusing, for similar reasons to yourself by the sounds of it.
"Service vs Library" sounds like 2 patterns being compared, this pattern is "Library" but that term doesn't describe this pattern well to me personally because it is applied more widely in our context.
I'd call this pattern "Separate Team Deployments" or maybe "By Use Deployments", and like your suggestion of "Separate Service Deployments".

Leggi il pattern Service vs. Library collegato nell’issue e la discussione correlata in #353. Confronta i nomi alternativi proposti e chiarisci quale nome corrisponde meglio al pattern; il lavoro è completato quando la questione dei nomi è risolta e il pattern è aggiornato di conseguenza.