goto / proton

This repository is home to the original protobuf interface definitions which are used throughout the gotocompany ecosystem.

Proton

This repository contains the original interface definitions of all APIs that support both REST and gRPC protocols. Reading the original interface definitions can provide a better understanding of APIs and help you to utilize them more efficiently. You can also use these definitions with open source tools to generate client libraries, documentation, and other artifacts.

Overview

The APIs are typically deployed as API services that are hosted under different DNS names. One API service may implement multiple APIs and multiple versions of the same API.

The APIs use Protocol Buffers version 3 (proto3) as their Interface Definition Language (IDL) to define the API interface and the structure of the payload messages. The same interface definition is used for both REST and RPC versions of the API, which can be accessed over different wire protocols.

There are several ways of accessing the APIs:

1. JSON over HTTP: You can access all APIs directly using JSON over HTTP, using any API client libraries.
2. Protocol Buffers over gRPC: You can access APIs published in this repository through GRPC, which is a high-performance binary RPC protocol over HTTP/2. It offers many useful features, including request/response multiplex and full-duplex streaming.

Structure

This repository uses a directory hierarchy that reflects the API product structure. In general, every API has its own root directory, and each major version of the API has its own subdirectory. The proto package names exactly match the directory: this makes it easy to locate the proto definitions and ensures that the generated client libraries have idiomatic namespaces in most programming languages.

Usage

Proton does not provide compiled language specific proto files or the descriptor sets for the respective protos. It is upto the users to pull these protos and use protoc or buf for language specific compiled files and have dependencies/imports in their code.

Guide

To generate gRPC source code for Google APIs in this repository, you first need to install buf on your local machine.

Generating go code using buf

This guide is last tried on buf version 1.5.0.

Add this buf.gen.yaml at the root folder.

version: v1beta1
plugins:
  - name: go
    out: dst
    opt: paths=source_relative

Run below command to generate your proto to /dst folder.

$ buf generate

Use below command if you just want to target specific package/folder

$ buf generate --path gotocompany/assets

Contribute

Prerequisites:

• Buf
• Git

You can run following command for linting protobuf files

$ buf lint

You can add proto files when you need to introduce proto for all projects. If you need to modify proto files, you need to ensure backward compatibility. To ensure the backward compatibility of your changes, you can run

$ buf breaking --against '.git#branch=master'

License

Proton is Apache 2.0 licensed.

proton's Issues

API support for assets

Is your feature request related to a problem? Please describe.
Current assets do not have support for http or grpc. We have firehoses writing to an api hence we need a feature to store api information as asset in compass.