Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

API: use gRPC and grpc-gateway #98

Closed
philips opened this issue Mar 15, 2016 · 0 comments
Closed

API: use gRPC and grpc-gateway #98

philips opened this issue Mar 15, 2016 · 0 comments
Labels
help wanted a good issue for non-maintainers to handle kind/feature request wishes for new functionality/docs
Milestone
v3.0.0

Comments

@philips
Copy link
Contributor

philips commented Mar 15, 2016

In many of our open source projects we are exposing API services we are starting to use gRPC and grpc-gateway. The advantage of using this framework instead of hand-rolled HTTP APIs are:

  • Codegen for the clients/servers
  • High efficiency gRPC based API available
  • Swagger codegen for REST API

This isn't high priority and should be something to consider for the v2 API or perhaps rebasing the v1 API to use it.
@philips philips added help wanted a good issue for non-maintainers to handle kind/feature request wishes for new functionality/docs component/api labels Mar 15, 2016
@jzelinskie jzelinskie added this to the 2.0 milestone Apr 18, 2016
KeyboardNerd added a commit to KeyboardNerd/clair that referenced this issue May 26, 2017
@KeyboardNerd
api: v2 api with gRPC and gRPC-gateway
623846d 
Newly designed API defines Ancestry as a set of layers
and shrinked the api to only the most used apis:
post ancestry, get layer, get notification, delete notification

Fixes quay#98
KeyboardNerd added a commit to KeyboardNerd/clair that referenced this issue May 31, 2017
@KeyboardNerd
api: v2 api with gRPC and gRPC-gateway
d5c53c9 
Newly designed API defines Ancestry as a set of layers
and shrinked the api to only the most used apis:
post ancestry, get layer, get notification, delete notification

Fixes quay#98
KeyboardNerd added a commit to KeyboardNerd/clair that referenced this issue May 31, 2017
@KeyboardNerd
api: v2 api with gRPC and gRPC-gateway
c9cc2fa 
Newly designed API defines Ancestry as a set of layers
and shrinked the api to only the most used apis:
post ancestry, get layer, get notification, delete notification

Fixes quay#98
@jzelinskie jzelinskie removed this from the 2.0 milestone Jun 1, 2017
KeyboardNerd added a commit to KeyboardNerd/clair that referenced this issue Jun 1, 2017
@KeyboardNerd
api: v2 api with gRPC and gRPC-gateway
efda069 
Newly designed API defines Ancestry as a set of layers
and shrinked the api to only the most used apis:
post ancestry, get layer, get notification, delete notification

Fixes quay#98
KeyboardNerd added a commit to KeyboardNerd/clair that referenced this issue Jun 1, 2017
@KeyboardNerd
api: v2 api with gRPC and gRPC-gateway
1b2de6d 
Newly designed API defines Ancestry as a set of layers
and shrinked the api to only the most used apis:
post ancestry, get layer, get notification, delete notification

Fixes quay#98
KeyboardNerd added a commit to KeyboardNerd/clair that referenced this issue Jun 2, 2017
@KeyboardNerd
api: v2 api with gRPC and gRPC-gateway
e87240f 
Newly designed API defines Ancestry as a set of layers
and shrinked the api to only the most used apis:
post ancestry, get layer, get notification, delete notification

Fixes quay#98
KeyboardNerd added a commit to KeyboardNerd/clair that referenced this issue Jun 2, 2017
@KeyboardNerd
api: v2 api with gRPC and gRPC-gateway
6b139e6 
Newly designed API defines Ancestry as a set of layers
and shrinked the api to only the most used apis:
post ancestry, get layer, get notification, delete notification

Fixes quay#98
KeyboardNerd added a commit to KeyboardNerd/clair that referenced this issue Jun 2, 2017
@KeyboardNerd
api: v2 api with gRPC and gRPC-gateway
c01a842 
Newly designed API defines Ancestry as a set of layers
and shrinked the api to only the most used apis:
post ancestry, get layer, get notification, delete notification

Fixes quay#98
KeyboardNerd added a commit to KeyboardNerd/clair that referenced this issue Jun 2, 2017
@KeyboardNerd
api: v2 api with gRPC and gRPC-gateway
d3f054f 
Newly designed API defines Ancestry as a set of layers
and shrinked the api to only the most used apis:
post ancestry, get layer, get notification, delete notification

Fixes quay#98
KeyboardNerd added a commit to KeyboardNerd/clair that referenced this issue Jun 2, 2017
@KeyboardNerd
api: v2 api with gRPC and gRPC-gateway
bbc7030 
Newly designed API defines Ancestry as a set of layers
and shrinked the api to only the most used apis:
post ancestry, get layer, get notification, delete notification

Fixes quay#98
KeyboardNerd added a commit to KeyboardNerd/clair that referenced this issue Jun 5, 2017
@KeyboardNerd
api: v2 api with gRPC and gRPC-gateway
8b72316 
Newly designed API defines Ancestry as a set of layers
and shrinked the api to only the most used apis:
post ancestry, get layer, get notification, delete notification

Fixes quay#98
KeyboardNerd added a commit to KeyboardNerd/clair that referenced this issue Jun 5, 2017
@KeyboardNerd
api: v2 api with gRPC and gRPC-gateway
da95bde 
Newly designed API defines Ancestry as a set of layers
and shrinked the api to only the most used apis:
post ancestry, get layer, get notification, delete notification

Fixes quay#98
KeyboardNerd added a commit to KeyboardNerd/clair that referenced this issue Jun 7, 2017
@KeyboardNerd
api: v2 api with gRPC and gRPC-gateway
5b2d7f7 
Newly designed API defines Ancestry as a set of layers
and shrinked the api to only the most used apis:
post ancestry, get layer, get notification, delete notification

Fixes quay#98
KeyboardNerd added a commit to KeyboardNerd/clair that referenced this issue Feb 2, 2018
@KeyboardNerd
api: v2 api with gRPC and gRPC-gateway
f633069 
Newly designed API defines Ancestry as a set of layers
and shrinked the api to only the most used apis:
post ancestry, get layer, get notification, delete notification

Fixes quay#98
@jzelinskie jzelinskie added this to the v3.0.0 milestone Oct 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
help wanted a good issue for non-maintainers to handle kind/feature request wishes for new functionality/docs
Milestone
v3.0.0
Development

No branches or pull requests
2 participants
@philips @jzelinskie