gRPC

Website

grpc.io

$ Details

Categories

#Web Servers #Web And Application Servers #Developer Tools #Load Balancer / Reverse Proxy

GitHub Flavored Markdown

Website

docs.github.com

$ Details

-

Categories

#Text Editors #Markdown Editor #Software Development #Developer Tools

gRPC features and specs

• Performance
  gRPC uses Protocol Buffers, which are more efficient in terms of serialization and deserialization compared to text-based formats like JSON. This leads to lower CPU usage and faster transmission, making it suitable for high-performance applications.
• Bi-directional Streaming
  gRPC supports bi-directional streaming, enabling both client and server to send a series of messages through a single connection. This is particularly useful for real-time communication applications.
• Strongly Typed APIs
  gRPC uses Protocol Buffers for defining service methods and message types, providing a strong type system that can catch potential issues at compile-time rather than runtime.
• Cross-language Support
  gRPC supports a wide range of programming languages, including but not limited to Java, C++, Python, Go, and C#. This allows for flexible integration in polyglot environments.
• Built-in Deadlines/Timeouts
  gRPC natively supports deadlines and timeouts to help manage long-running calls and avoid indefinite blocking, improving robustness and reliability.
• Automatic Code Generation
  gRPC provides tools for automatic code generation from .proto files, reducing boilerplate code and speeding up the development process.

Possible disadvantages of gRPC

• Learning Curve
  The complexity of gRPC and Protocol Buffers may present a steep learning curve for developers who are not familiar with these technologies.
• Limited Browser Support
  gRPC was not originally designed with browser support in mind, making it challenging to directly call gRPC services from web applications without additional tools like gRPC-Web.
• Verbose Configuration
  Setting up gRPC and defining .proto files can be more verbose compared to simpler RESTful APIs, which might be a deterrent for smaller projects.
• HTTP/2 Requirement
  gRPC relies on HTTP/2 for transport, which can be problematic in environments where HTTP/2 is not supported or requires additional configuration.
• Limited Monitoring and Debugging Tools
  Compared to REST, there are fewer tools available for monitoring, debugging, and testing gRPC services, which might complicate troubleshooting and performance tuning.
• Protobuf Ecosystem Requirement
  Depending on the language, integrating Protocol Buffers might require additional dependencies and tooling, which could add to the maintenance overhead.

GitHub Flavored Markdown features and specs

• Widespread Usage
  GitHub Flavored Markdown (GFM) is widely used in the GitHub community, making it a popular choice for collaborating on open-source projects and documenting code repositories.
• Enhanced Features
  GFM extends the standard Markdown with additional features like tables, strikethrough, and syntax highlighting, allowing for more expressive and informative content.
• Version Control Integration
  GFM is seamlessly integrated with GitHub’s version control system, making it easy to track changes, collaborate on documentation, and propose updates through pull requests.
• Live Preview
  GitHub provides a live preview of Markdown files, which helps users see how their Markdown will render, ensuring the final document looks as expected.
• Cross-Platform Compatibility
  Since GFM is based on Markdown, documents can be easily shared and rendered across different platforms and services, retaining consistent formatting.

Possible disadvantages of GitHub Flavored Markdown

• Limited Advanced Formatting
  While GFM offers several enhancements over standard Markdown, it still lacks support for some advanced formatting options found in richer text editors or other markup languages.
• GitHub Dependency
  GFM is primarily designed to work within the GitHub ecosystem, which can limit usefulness outside of GitHub, especially if using features specific to GFM.
• Learning Curve
  Users familiar with standard Markdown might need to learn the additional syntax and features of GFM, which can be an initial barrier for some.
• Consistency Issues
  Rendering consistency might vary when GFM documents are viewed outside of GitHub, as some features might not be supported in other Markdown processors.

gRPC, Protobufs and Go... OH MY! An introduction to building client/server systems with gRPC

More videos:

Demystifying Markdown – Learn GitHub flavored Markdown (GFM) on Skillshare | Clyde D'Souza