-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Comments
can we have a TODO list about gRPC backend?
|
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. |
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. |
Also curious to know what the status is, would like to support Protobuf too. |
Nobody has had time to drive this to completion yet. So the unchecked boxes still need to get resolved. |
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.
The text was updated successfully, but these errors were encountered: