gRPC VS linkerd

gRPC Reviews

linkerd Reviews

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 / 4 months ago

linkerd mentions (15)

• Optimal JMX Exposure Strategy for Kubernetes Multi-Node Architecture

  Leverage a service mesh like Istio or Linkerd to manage communication between microservices within the Kubernetes cluster. These service meshes can be configured to intercept JMX traffic and enforce access control policies. Benefits:. - Source: dev.to / about 1 month ago

• Ultimate EKS Baseline Cluster: Part 1 - Provision EKS

  From here, we can explore other developments and tutorials on Kubernetes, such as o11y or observability (PLG, ELK, ELF, TICK, Jaeger, Pyroscope), service mesh (Linkerd, Istio, NSM, Consul Connect, Cillium), and progressive delivery (ArgoCD, FluxCD, Spinnaker). - Source: dev.to / 10 months ago

• Istio moved to CNCF Graduation stage

  Https://linkerd.io/ is a much lighter-weight alternative but you do still get some of the fancy things like mtls without needing any manual configuration. Install it, label your namespaces, and let it do it's thing! - Source: Hacker News / 10 months ago

• API release strategies with API Gateway

  Open source API Gateway (Apache APISIX and Traefik), Service Mesh (Istio and Linkerd) solutions are capable of doing traffic splitting and implementing functionalities like Canary Release and Blue-Green deployment. With canary testing, you can make a critical examination of a new release of an API by selecting only a small portion of your user base. We will cover the canary release next section. - Source: dev.to / over 1 year ago

• GKE with Consul Service Mesh

  I have experimented with other service meshes and I was able to get up to speed quickly: Linkerd = 1 day, Istio = 3 days, NGINX Service Mesh = 5 days, but Consul Connect service mesh took at least 11 days to get off the ground. This is by far the most complex solution available. - Source: dev.to / over 1 year ago