DokumentePreiseBlog
Kontaktieren Sie uns
AnmeldenKOSTENLOS anmelden
Back to Tech Articles

Building Dual-Purpose APIs with Go Protobuf and gRPC-Gateway

Sept. 12, 2025
# Misc

James Reed

Infrastructure Engineer · Leapcell

Dieser Beitrag ist auch in 日本語, 한국어 und Deutsch verfügbar
Cover of "Building Dual-Purpose APIs with Go Protobuf and gRPC-Gateway"

Introduction

In today's interconnected software landscape, microservices architectures and diverse client applications are the norm. This often presents a challenge: how do we build APIs that are performant and type-safe for internal service-to-service communication, yet also accessible and idiomatic for external web-based clients? Traditional RESTful APIs might suffice for external consumers, but they often lack the strong typing and efficiency desired for inter-service communication. Conversely, pure gRPC excels in internal scenarios but isn't directly consumable by web browsers. This article delves into a powerful solution using Go, Google's Protocol Buffers (Protobuf), and gRPC-Gateway to create a single source of truth for your API definitions that gracefully serves both internal gRPC consumers and external RESTful clients. We'll explore how this combination simplifies development, reduces redundancy, and fosters a more maintainable and scalable API ecosystem.

Core Concepts

Before we dive into the implementation, let's establish a clear understanding of the key technologies involved:

  • Protocol Buffers (Protobuf): A language-agnostic, platform-agnostic, extensible mechanism for serializing structured data. Protobuf defines a schema for your data using .proto files, acting as an Interface Definition Language (IDL). From this schema, compilers generate code in various languages (like Go) for marshaling and unmarshaling data. Its binary serialization is highly efficient, making it ideal for high-performance communication.

  • gRPC: A high-performance, open-source universal RPC framework. Built on Protobuf, gRPC automatically handles serialization, network communication, and method invocation. It supports features like streaming, authentication, and load balancing, making it a robust choice for inter-service communication. Its strong typing derived from Protobuf ensures compile-time checks and reliable data contracts.

  • gRPC-Gateway: A plugin for the Protobuf compiler that generates a reverse proxy server. This proxy translates HTTP/JSON requests into gRPC requests and then forwards them to your actual gRPC service. It also translates the gRPC responses back into HTTP/JSON responses. Essentially, gRPC-Gateway allows you to expose your gRPC services as conventional RESTful APIs, making them consumable by web browsers and other HTTP clients without requiring specific gRPC client libraries.

Building Dual-Purpose APIs

The core idea behind this approach is to define your API once using Protobuf. This single definition then serves as the contract for both your gRPC service and its RESTful counterpart generated by gRPC-Gateway.

1. Define Your API with Protobuf

Let's start by defining a simple API for a "Todo" service. Create a file named proto/todo/todo.proto:

syntax = "proto3";

package todo;

option go_package = "github.com/your/repo/gen/proto/go/todo";

import "google/api/annotations.proto";

service TodoService {
  rpc CreateTodo(CreateTodoRequest) returns (Todo) {
    option (google.api.http) = {
      post: "/v1/todos"
      body: "*"
    };
  }
  rpc GetTodo(GetTodoRequest) returns (Todo) {
    option (google.api.http) = {
      get: "/v1/todos/{id}"
    };
  }
  rpc ListTodos(ListTodosRequest) returns (ListTodosResponse) {
    option (google.api.http) = {
      get: "/v1/todos"
    };
  }
}

message Todo {
  string id = 1;
  string title = 2;
  string description = 3;
  bool completed = 4;
}

message CreateTodoRequest {
  string title = 1;
  string description = 2;
}

message GetTodoRequest {
  string id = 1;
}

message ListTodosRequest {
}

message ListTodosResponse {
  repeated Todo todos = 1;
}

Notice the google/api/annotations.proto import and the option (google.api.http) annotations. These are crucial for gRPC-Gateway. They define how your gRPC methods map to HTTP methods, paths, and request/response bodies.

2. Generate Go Code

Next, you need to compile your Protobuf definitions into Go code. This requires protoc and the Go Protobuf and gRPC plugins, along with the gRPC-Gateway plugin. Assuming you have these installed, you might use a Makefile or a script for compilation:

# Install protoc-gen-go, protoc-gen-go-grpc, protoc-gen-grpc-gateway, protoc-gen-openapiv2
# go install google.golang.org/protobuf/cmd/protoc-gen-go@latest
# go install google.golang.org/grpc/cmd/protoc-gen-go-grpc@latest
# go install github.com/grpc-ecosystem/grpc-gateway/v2/protoc-gen-grpc-gateway@latest
# go install github.com/grpc-ecosystem/grpc-gateway/v2/protoc-gen-openapiv2@latest

mkdir -p gen/proto/go/todo

protoc -I. \
  -I/usr/local/include \
  -I$(go env GOPATH)/src \
  -I$(go env GOPATH)/pkg/mod \
  --go_out=paths=source_relative:gen/proto/go \
  --go-grpc_out=paths=source_relative:gen/proto/go \
  --grpc-gateway_out=paths=source_relative:gen/proto/go \
  --openapiv2_out=gen/proto/openapiv2 \
  proto/todo/todo.proto

This command generates several files:

  • gen/proto/go/todo/todo.pb.go: Contains the Protobuf message structs and helper functions.
  • gen/proto/go/todo/todo_grpc.pb.go: Contains the gRPC service interface and client/server stubs.
  • gen/proto/go/todo/todo.pb.gw.go: The gRPC-Gateway reverse proxy code.
  • gen/proto/openapiv2/todo/todo.swagger.json: OpenAPI/Swagger documentation (optional but very useful!).

3. Implement the gRPC Service

Now, implement the actual business logic for your TodoService.

// main.go (simplified for illustration)
package main

import (
	"context"
	"log"
	"net"
	"net/http"
	"os"

	"github.com/grpc-ecosystem/grpc-gateway/v2/runtime"
	"google.golang.org/grpc"
	"google.golang.org/grpc/credentials/insecure"

	pb "github.com/your/repo/gen/proto/go/todo"
)

// todoService implements the gRPC TodoService interface
type todoService struct {
	pb.UnimplementedTodoServiceServer // Embed for forward compatibility
}

func NewTodoService() *todoService {
	return &todoService{}
}

func (s *todoService) CreateTodo(ctx context.Context, req *pb.CreateTodoRequest) (*pb.Todo, error) {
	log.Printf("Received CreateTodo request: %v", req)
	// In a real application, you'd store this in a database
	return &pb.Todo{
		Id:          "id-generated-123", // Simulate ID generation
		Title:       req.GetTitle(),
		Description: req.GetDescription(),
		Completed:   false,
	}, nil
}

func (s *todoService) GetTodo(ctx context.Context, req *pb.GetTodoRequest) (*pb.Todo, error) {
	log.Printf("Received GetTodo request: %v", req)
	// Simulate fetching from DB
	if req.GetId() == "id-generated-123" {
		return &pb.Todo{
			Id:          "id-generated-123",
			Title:       "My First Todo",
			Description: "This is a detailed description.",
			Completed:   false,
		}, nil
	}
	return nil, grpc.Errorf(codes.NotFound, "Todo with ID %s not found", req.GetId())
}

func (s *todoService) ListTodos(ctx context.Context, req *pb.ListTodosRequest) (*pb.ListTodosResponse, error) {
	log.Printf("Received ListTodos request")
	// Simulate fetching all todos
	return &pb.ListTodosResponse{
		Todos: []*pb.Todo{
			{Id: "id-generated-123", Title: "My First Todo", Description: "Description 1", Completed: false},
			{Id: "id-456", Title: "Buy groceries", Description: "Milk, eggs, bread", Completed: true},
		},
	}, nil
}

func main() {
	grpcPort := ":8080"
	httpPort := ":8081"

	// Start gRPC server
	lis, err := net.Listen("tcp", grpcPort)
	if err != nil {
		log.Fatalf("failed to listen: %v", err)
	}
	s := grpc.NewServer()
	pb.RegisterTodoServiceServer(s, NewTodoService())
	log.Printf("gRPC server listening on %s", grpcPort)
	go func() {
		if err := s.Serve(lis); err != nil {
			log.Fatalf("Failed to serve gRPC: %v", err)
		}
	}()

	// Start gRPC-Gateway proxy
	ctx := context.Background()
	ctx, cancel := context.WithCancel(ctx)
	defer cancel()

	mux := runtime.NewServeMux()
	opts := []grpc.DialOption{grpc.WithTransportCredentials(insecure.NewCredentials())}
	err = pb.RegisterTodoServiceHandlerFromEndpoint(ctx, mux, "localhost"+grpcPort, opts)
	if err != nil {
		log.Fatalf("Failed to register gateway: %v", err)
	}

	log.Printf("gRPC-Gateway server listening on %s", httpPort)
	if err := http.ListenAndServe(httpPort, mux); err != nil {
		log.Fatalf("Failed to serve gRPC-Gateway: %v", err)
	}
}

This main.go sets up two servers:

  • A gRPC server listening on port 8080, which implements our TodoService.
  • A gRPC-Gateway proxy server listening on port 8081. This server takes HTTP/JSON requests and forwards them to the gRPC server.

4. Application Scenarios

With this setup, you can now:

  • Internal Microservices: Other Go microservices can communicate directly with your TodoService using gRPC on localhost:8080. They benefit from strong typing, efficient binary serialization, and gRPC's advanced features.

    // Internal gRPC client example
package main

import (
	"context"
	"log"

	"google.golang.org/grpc"
	"google.golang.org/grpc/credentials/insecure"

	pb "github.com/your/repo/gen/proto/go/todo"
)

func main() {
	conn, err := grpc.Dial("localhost:8080", grpc.WithTransportCredentials(insecure.NewCredentials()))
	if err != nil {
		log.Fatalf("did not connect: %v", err)
	}
	defer conn.Close()
	client := pb.NewTodoServiceClient(conn)

	res, err := client.CreateTodo(context.Background(), &pb.CreateTodoRequest{
		Title:       "Internal Todo",
		Description: "Created via gRPC",
	})
	if err != nil {
		log.Fatalf("could not create todo: %v", err)
	}
	log.Printf("Created Todo (gRPC): %v", res)
}

  • External Web Clients: Web browsers, mobile apps, or other external systems can interact with your service using standard HTTP/JSON requests on localhost:8081.

    # Example using curl for HTTP/JSON
curl -X POST -H "Content-Type: application/json" \
     -d '{"title": "External Todo", "description": "Created via HTTP"}' \
     http://localhost:8081/v1/todos

# Output:
# {"id":"id-generated-123","title":"External Todo","description":"Created via HTTP","completed":false}

curl http://localhost:8081/v1/todos/id-generated-123

# Output:
# {"id":"id-generated-123","title":"My First Todo","description":"This is a detailed description.","completed":false}

curl http://localhost:8081/v1/todos
# Output:
# {"todos":[{"id":"id-generated-123","title":"My First Todo","description":"Description 1","completed":false},{"id":"id-456","title":"Buy groceries","description":"Milk, eggs, bread","completed":true}]}

Conclusion

By leveraging Go, Protocol Buffers, and gRPC-Gateway, you can establish a single, robust API definition (.proto file) that generates boilerplate code for both high-performance gRPC services and universally accessible RESTful HTTP/JSON endpoints. This approach significantly reduces duplication, improves consistency across different consumer types, and streamlines API development and maintenance. With this powerful combination, you can build APIs that are both highly efficient for internal communication and effortlessly friendly for external clients, truly achieving the best of both worlds.

Share this article

HackerNews

More Posts from Leapcell

Popular Posts