JSON VS gRPC

JSON Reviews

gRPC Reviews

JSON mentions (13)

• The Last Breaking Change | JSON Schema Blog

  The YAML 0.1 spec was sent to a public user group in May 2001. JSON was named in a State Software internal discussion. State Software was founded in March 2001. json.org was launched in 2002. Therefore you’re just wrong: YAML came out before JSON. Source: about 1 year ago

• Why does wine give warnings about using 64bit prefixes, or has 32bit packages? Hasn't the world moved on from 32 bit a century ago?

  How come that doesn't apply to other libraries? For example, when I write Java or Node.js programs, I don't need to make sure packages like json.org or express.js have a 32bit or 64bit environment. What makes windows libs different than NPM libs? Source: over 1 year ago

• “Ignore the f'ing haters ” And other lessons learned from creating a popular

  The first two sentences of the text on http://json.org are "JSON (JavaScript Object Notation) is a lightweight data-interchange format. It is easy for humans to read and write." It's a primary goal of JSON, it's fair to question whether it's successful at it. Personally, I'd much rather write TOML or S expressions. I don't like YAML at all, the whitespace sensitivity drives me nuts. - Source: Hacker News / over 1 year ago

• Recording your JSON data to MCAP, a file format that support multiple serialization formats

  To help you make the transition, we’ve written a tutorial on how to write an MCAP writer in Python to record JSON data to an MCAP file. Source: almost 2 years ago

• replace \" with "

  What you need to probably do is to step back and learn the format for JSON, and the core data structures that you will find in most languages:. Source: almost 2 years ago

gRPC mentions (86)

• Golang: out-of-box backpressure handling with gRPC, proven by a Grafana dashboard

  gRPC, built on HTTP/2, inherently supports flow control. The server can push updates, but it must also respect flow control signals from the client, ensuring that it doesn't send data faster than what the client can handle. - Source: dev.to / about 1 month ago

• Delving Deeper: Enriching Microservices with Golang with CloudWeGo

  While gRPC and Apache Thrift have served the microservice architecture well, CloudWeGo's advanced features and performance metrics set it apart as a promising open source solution for the future. - Source: dev.to / 2 months ago

• Dart on the Server: Exploring Server-Side Dart Technologies in 2024

  The Dart implementation of gRPC which puts mobile and HTTP/2 first. It's built and maintained by the Dart team. Grpc is a high-performance RPC (remote procedure call) framework that is optimized for efficient data transfer. - Source: dev.to / 3 months ago

• How to Build & Deploy Scalable Microservices with NodeJS, TypeScript and Docker || A Comprehesive Guide

  gRPC is a high-performance, open-source RPC (Remote Procedure Call) framework initially developed by Google. It uses Protocol Buffers for serialization and supports bidirectional streaming. - Source: dev.to / 3 months ago

• Actual SSH over HTTPS

  In general, tunneling through HTTP2 turns out to be a great choice. There is a RPC protocol built on top of HTTP2: gRPC[1]. This is because HTTP2 is great at exploiting a TCP connection to transmit and receive multiple data structures concurrently - multiplexing. There may not be a reason to use HTTP3 however, as QUIC already provides multiplexing. I expect that in the future most communications will be over... - Source: Hacker News / 5 months ago