feat: add grpc to glossary

[Sonichigo]

Describe your changes

This pull request adds a new conceptual documentation page for gRPC, covering its purpose, benefits, and use cases in modern distributed systems and microservices architectures.

• Added content/en/grpc.md to provide an overview of gRPC, including its architecture (HTTP/2, Protocol Buffers), the problems it solves in distributed systems, and its advantages for microservices, streaming, and interoperability.

Related issue number or link (ex: resolves #issue-number)

resolves #1038

Checklist before opening this PR (put x in the checkboxes)

• This PR does not contain plagiarism
  • don’t copy other people’s work unless you are quoting and contributing it to them.
• I have signed off on all commits
  • signing off (ex: git commit -s) is to affirm that commits comply DCO. If you are working locally, you could add an alias to your gitconfig by running git config --global alias.ci "commit -s".

[netlify]

✅ Deploy Preview for cncfglossary ready!

Name	Link
🔨 Latest commit	aa3c987
🔍 Latest deploy log	https://app.netlify.com/projects/cncfglossary/deploys/6993175b551e6e00080f9692
😎 Deploy Preview	https://deploy-preview-3551--cncfglossary.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[chalin]

Nice idea to add gRPC.
Can someone from the gRPC team review this? @gnossen @ejona86 @thisisnotapril

See inline comments.

/cc @nate-double-u

[Sonichigo]

@chalin I have resolved the comments!

@gnossen @ejona86 @thisisnotapril can I get feedback/suggestion on this PR?

[Sonichigo]

@iamNoah1 @nate-double-u can i get review?

[iamNoah1]

@Sonichigo Thanks a lot for tackling this term and the effort you put in it. While it might be technically accurate I find it very complex to read. It references a lot of other technical terms, making it hard to understand for someone who is maybe not so much a technical person. Even if, it is not easy.
My encouragement is to double check on our styleguide: https://glossary.cncf.io/style-guide/ to understand how we want terms to be described ideally.
Please also pay attention to use semantic line breaks.

[hlipsig]

Agreed with the previous review. Fantastic idea to include gPRC and an excellent effort. However, I also agree it's diffficult to understand without more of an anchor. I suspect this article could benefit from a comparison to help readers understand the why of gRPC. For example what the alternatives are and a more concise example of a use case in the "How it helps" section.

[jihoon-seo]

The links are not working as-is.

[chalin]

@Sonichigo - can you address the comments?

[GoldenLion7]

@chalin may I give it a try?

[GoldenLion7]

Anyone or @chalin I want to help with documentation or if anything else open and u want me to work upon

[Sonichigo]

@chalin may I give it a try?

Hi @GoldenLion7 I'm still working on this one. You can pickup issues relevant from here - https://github.com/cncf/glossary/issues?q=is%3Aissue%20state%3Aopen%20no%3Aassignee

[GoldenLion7]

@Sonichigo no worries, go ahead. Take your time :)

[Sonichigo]

@nate-double-u can you check the following PR. I have updated it based on the guidelines and suggestion based on earlier reviewer's left has previously been included.

[nate-double-u]

Hi @Sonichigo, thanks for the updates.

This is quite long for one of our definitions. Please take a look at some of our other work to get a sense of how long a definition should be.

This still doesn't follow our style guide:

• For instance, the gRPC vs. Alternatives section doesn't show up in any of our other work and should be omitted here.
• Things like contractions should be avoided, generally. You can also find a list of tags there (the tags in this definition don't quite match up).
• In the Problem it addresses section, avoid mentioning the term that is being defined, this section helps folks understand what led to needing the thing.