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.

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

Support gRPC backend #582

Open
flier opened this issue Jun 30, 2016 · 5 comments · May be fixed by #583
Open

Support gRPC backend #582

flier opened this issue Jun 30, 2016 · 5 comments · May be fixed by #583

Comments

@flier
Copy link

flier commented Jun 30, 2016

Problem statement

As you know, gRPC provides more powerful and faster API mechanism base on HTTP/2.0 with protobuf encoding than HTTP/HTTPS with JSON/XML encoding.

I'm working on a faster prototype to implement gRPC backend base on go-swagger, it could works to generate probobuf schema and server side code.

If you think it is ok, we may put more efforts on it.

@flier flier linked a pull request Jun 30, 2016 that will close this issue
@flier
Copy link
Author

flier commented Jul 4, 2016

can we have a TODO list about gRPC backend?

  • generate protobuf file base on schema
  • generate gRPC service server stub
  • generate gRPC service client stub
  • validate parameters base on schema
  • use TLS based secure connection in gRPC
  • support stream based parameter
  • support middleware
  • export generated .proto file
  • migrate templates to use go 1.5 or earlier syntax
  • add/update gRPC examples
  • performance test tool/reports

@casualjim
Copy link
Member

this todo list looks OK, you don't need to move to pre 1.6 template support.Dropping support for building on 1.5 is fine.
I only want to do current + 1 prior. In august there is 1.7 so I don't see a pressing need to end up with messier templates :)

@coccyx
Copy link

coccyx commented Jan 17, 2017

Did this ever go anywhere? A few of the services we're building will suffer from a large penalty from the serialization costs of JSON versus something like Protobuf so we've been considering gRPC. We'd like to continue to define the APIs via Swagger and translate. There are some other initiatives to take Protobufs and generate Swagger which is also an option, but remaining with go-swagger would be the most preferable.

@bobvanluijt
Copy link
Contributor

Also curious to know what the status is, would like to support Protobuf too.

@casualjim
Copy link
Member

Nobody has had time to drive this to completion yet. So the unchecked boxes still need to get resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants