Naming of the Service vs. Library pattern

未關閉

#355 建立於 2021年9月13日 7 則留言 0 個 reaction 已指派 0 人在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度: 5/5
預估耗時: 一週以上
新手友好度: 20/100

Issue 類型: 文件
描述清晰度: 需要釐清
活躍度: 停滯
領域: documentation

研究方向

閱讀 issue 中連結的 Service vs. Library pattern，以及 #353 中的相關討論。比較提出的替代名稱，並釐清哪個名稱最符合該 pattern；命名問題獲得解決並據此更新 pattern 後，即視為完成。

由索引模型根據 Issue 內容生成。

描述

:book: Type - Content Work

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".

主要語言: HTML
星號: 853
分支: 206
平均合併: 1 天 23 小時
30 天內合併 PR: 2