pattern/service-vs-library about innersourcepatterns

[NewMexicoKid]

Isabel, I would encourage you to write this up in a pattern format.

[rrrutledge]

Sounds interesting

[chchrist]

@MaineC we have a team that developed a service that acts as a facade for another third party SaaS so in the future we could switch to a new same type SaaS without much overhead. Now other teams want to start using this service but the original team does not want to be responsible for problems that other teams might introduce. Does the above pattern fits this case? Does that mean that each new team will have to deploy their own service that does something similar?

[lenucksi]

@MaineC we have a team that developed a service that acts as a facade for another third party SaaS so in the future we could switch to a new same type SaaS without much overhead. Now other teams want to start using this service but the original team does not want to be responsible for problems that other teams might introduce. Does the above pattern fits this case? Does that mean that each new team will have to deploy their own service that does something similar?

Hey @chchrist, thanks for bringing this up! 👍
I think given the short form of "InnerSource not InnerDeployment" this might be interesting. There is also a mention of the "30 days of warranty" pattern in the linked PR discussion that might be of interest to you.

I've also posted a link to your question to our Slack - you are very much invited to join there for more discussion.