Did you use both gRPC and REST or only gRPC?

In my practice, I have used both approaches — gRPC and REST, depending on the project requirements.

gRPC is well-suited for high-performance microservices with clearly defined contracts, where speed and binary protocol are important. For example, for internal communication between services in a distributed system.

REST was more often used for external APIs, where simplicity, browser compatibility, and broad HTTP support are important.

Example of using gRPC in Go:

import (
    "context"
    "google.golang.org/grpc"
    pb "path/to/protobuf/package"
)

func main() {
    conn, err := grpc.Dial("localhost:50051", grpc.WithInsecure())
    if err != nil {
        panic(err)
    }
    defer conn.Close()

    client := pb.NewYourServiceClient(conn)
    resp, err := client.YourMethod(context.Background(), &pb.YourRequest{})
    if err != nil {
        panic(err)
    }
    fmt.Println(resp)
}

Thus, the choice between gRPC and REST depends on specific requirements: gRPC — for internal, high-performance interaction, REST — for public APIs and ease of integration.