Google has open-sourced something called “gRPC” that it says represents “a brand new framework for handling remote procedure calls” using HTTP/2.
The Chocolate Factory says it has dogfooded gRPC on its own microservices and that it “enables easy creation of highly performant, scalable APIs and microservices” and offers “bandwidth and CPU efficient, low latency way to create massively distributed systems that span data centers, as well as power mobile apps, real-time communications, IoT devices and APIs.”
HTTP/2's inclusion is important, Google reckons, because the newly-signed-off standard can pack more jobs into a single TCP connection, which means less work for a mobile device's innards to perform and therefore helps battery life.
Developers wielding C, C++, Java, Go, Node.js, Python, and Ruby can put the package to work. Objective-C, PHP and C# users have a yet-to-be-defined amount of time to wait before unleasing their preferred syntax.
Does the world need another RPC framework? And does HTTP/2 really make a difference to such efforts? Google may not care: this one looks less like it steers developers towards Google-land than other Chocolate Factory efforts. Whether developers care will soon become apparent on GitHub, where gRPC can be found and footled. ®