yzeng25 commented on pull request #4546: URL: https://github.com/apache/apisix/pull/4546#issuecomment-875582063
> > I think it's not appropriate to call it "后端服务" since there is no "前端". Maybe call it "上游" is more accurate > > If we decide to use the term "上游"，then we may use it everywhere of our documentations. > > By the way, a glossary might be required. Yes, this PR uses "Upstream" **everywhere in 'Getting-Started' document**, except 2-3ish places where it needs to explain what is an "Upstream", or give a synonym of "Upstream". The current situation is that "Upstream", "后端服务" and other words are referencing to the same thing with different names (Maybe they do have some tiny differences after all). Thus, it creates confusion for me to read, identify and understand this document. This then brings up more abstracted problems: 1. Similarly, here is what I would ask: is there an "upstream" since there is no "downstream"? which of the following is more broadly accepted, "后端服务", or "上游"? 2. Where is the glossary? Yes, we definitely need a glossary to explain and define frequently used words and phrases. But it is not my top priority task yet. 2. How many other places are referencing the same thing with different names? I don't know, it is just a matter of time to find out and fix them. 3. Why this change is only made in 'Getting-Started' document'? Well, it is the very first document page or the 'entry' of all Apache APISIX documents. I want this page to be somewhat helpful and impressing. 4. Are we missing other sorts of documents? Along with Q1 and Q3, my answer is yes. We definitely need a product overview, product architecture, glossary, etc, to form a series of 'Product Introduction' documents. And we do need other series of documents as well. The reason why I am not doing this right now is that I am new to this team, and I want to find out how can I make good use of the existing documents. Hope this clarifies your concerns. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
