Trends is free while in Beta
18%
(5y)
8%
(1y)
15%
(3mo)

About gRPC

gRPC is a high performance, open source RPC framework developed by Google that uses HTTP/2 for transport, Protocol Buffers for serialization, and supports multiple languages for communication between microservices and client server applications.

Trend Decomposition

Trend Decomposition

Trigger: Enterprise microservices adoption and need for efficient, strongly typed cross language RPC communication.

Behavior change: Teams adopt gRPC for inter service calls, streaming capabilities, and polyglot service ecosystems.

Enabler: HTTP/2, Protocol Buffers, broad language support, and strong ecosystem tooling and documentation.

Constraint removed: Reduced overhead from JSON over HTTP/2; improved streaming, multiplexing, and contract first API design.

PESTLE Analysis

PESTLE Analysis

Political: Standardization and vendor neutrality promote open source adoption across industries.

Economic: Efficiency gains reduce latency and network costs in large scale microservice environments.

Social: Enables more reliable real time and streaming interactions between services, improving user experiences.

Technological: Advances in code generation, multi language support, and ecosystem integrations boost adoption.

Legal: Open source licensing considerations and compliance frameworks govern usage.

Environmental: Potential indirect reductions in infrastructure energy use due to lower overhead and better streaming efficiency.

Jobs to be done framework

Jobs to be done framework

What problem does this trend help solve?

It solves efficient, type safe, multi language remote procedure calls between microservices and clients.

What workaround existed before?

REST/JSON or custom RPC protocols with higher overhead and less efficient streaming.

What outcome matters most?

Speed and reliability of inter service communication with lower latency and stronger contracts.

Consumer Trend canvas

Consumer Trend canvas

Basic Need: Efficient, scalable system to system communication.

Drivers of Change: Microservices architecture, multi language environments, demand for streaming RPC.

Emerging Consumer Needs: Faster feature delivery, real time data, reliable cross language calls.

New Consumer Expectations: Consistency, low latency, and strong API contracts across services.

Inspirations / Signals: Adoption by major tech companies, open source momentum, and robust tooling.

Innovations Emerging: gRPC Web, service definitions with Protocol Buffers, code generation in multiple languages.

Companies to watch

Associated Companies
  • Google - Original creator and primary maintainer of gRPC; extensive internal and external use.
  • Netflix - Uses gRPC in microservices to improve performance and streaming capabilities.
  • Dropbox - Adopted gRPC for efficient internal service communication and scaling.
  • Lyft - Utilizes gRPC in microservice communications to enhance throughput.
  • Square - Leveraged gRPC for scalable, language diverse service APIs.