Best of gRPC2023

  1. 1
    Article
    Avatar of amplicationAmplication·3y

    REST vs. gRPC - What’s the Difference?

    REST has been around for a long time and is an industry standard for developing and designing APIs. Google Remote Procedure Call, or gRPC, was created on top of the RPC protocol. The Amplication repository is about to hit 10,000-stars on GitHub.

  2. 2
    Article
    Avatar of bytebytegoByteByteGo·3y

    EP49: API Architectural Styles

    This week’s system design refresher: API architectural styles. EP49: API Architectural Styles. How Levels.fyi scaled to millions of users using Google Sheets as a backend. Backend burger: How to use New Relic to achieve Kubernetes observability.

  3. 3
    Article
    Avatar of bytebytegoByteByteGo·3y

    Network Protocols behind Server Push, Online Gaming, and Emails

    The focus here is on understanding how different protocols shape the way we communicate and interact over the Internet. We will dive into the following areas: The process through which servers can proactively send updates to clients using WebSockets. The reason behind the choice of UDP protocol in gaming applications and how its reliability can be enhanced.

  4. 4
    Article
    Avatar of infoqInfoQ·2y

    Why LinkedIn chose gRPC+Protobuf over REST+JSON: Q&A with Karthik Ramgopal and Min Chen

    LinkedIn explains why they chose gRPC and Protocol Buffers over REST and JSON for inter-service communication in their microservices platform. They observed significant latency improvements and are advising Rest.li users to migrate to gRPC.

  5. 5
    Article
    Avatar of dzDZone·3y

    gRPC vs. REST

    This post compares the architectures of gRPC and REST for client-server communication. It discusses the strengths and weaknesses of each architecture, as well as their use cases. It also highlights the technical differences between gRPC and REST, such as the message format, protocol, latency, payload limit, security, and speed. The post concludes by stating that while REST is still the most popular architecture, gRPC is well-suited for high-workload applications.

  6. 6
    Article
    Avatar of logrocketLogRocket·3y

    Communicating between Node.js microservices with gRPC

    Learn how to use gRPC in Node.js for inter-microservice communication by building a practical communication system for three microservices. The @grpc/grpc-js package offers a fully-featured, official, pure JavaScript implementation of the gRPC framework concept.

  7. 7
    Article
    Avatar of dzDZone·3y

    Understanding gRPC Concepts, Use Cases, and Best Practices

    In this article, we are going to understand what RPC is, and the various implementations of RPC, with a focus on gRPC, which is Google's implementation of RPC. RPC stands for Remote Procedure Calls; it's the "Remote" word that makes all the difference. Join the DZone community and get the full member experience.

  8. 8
    Article
    Avatar of glcGolang News·3y

    A Golang based open-source, self-hosted feature flag application

    Flipt is an open-source, self-hosted feature flag application that allows you to run experiments across services in your environment. It can be deployed within your existing infrastructure so that you don’t have to worry about your information being sent to a third party or the latency required to communicate across the internet.

  9. 9
    Article
    Avatar of trendyoltechTrendyol Tech·3y

    gRPC with GoLang

    gRPC is an open-source remote procedure call (RPC) framework developed by Google. It supports multiple programming languages and communication patterns, and provides high-performance and efficient communication. gRPC uses Protocol Buffers (protobuf) for data serialization and supports streaming for real-time communication. Key differences between gRPC and REST include API style, serialization, transport protocol, language support, and streaming support.

  10. 10
    Article
    Avatar of itnextITNEXT·3y

    Enhancing gRPC Error Handling in a Microservice Architecture

    Enhancing gRPC Error Handling in a Microservice Architecture is a crucial part of software engineering. Poorly returned errors and non-informative ones can cause unimaginable headaches. The most simplistic way to return an error in an RPC might be as follows: It provides nearly zero information to the caller about what went wrong and why.

  11. 11
    Article
    Avatar of semaphoreSemaphore·3y

    Microservices Communication in NestJS With gRPC

    The goal is to create a complete meal by combining all these dishes. Each dish represents a microservice with a specific function or purpose. In a microservices architecture, developers can develop, deploy, and maintain each microservice independently from the others. We can ensure that microservices can function seamlessly to build a durable and scalable system.