Analyzing the OpenAPI Tooling Ecosystem

Re:Analyzing the OpenAPI Tooling Ecosystem by cdelsolar on Tuesday September 24, 2024 @04:15PM (#41640436)

Yep, but the awesomeness of ConnectRPC is that you can use the JSON api in the web browser, and indeed I do that in this project. We don't have to, and as a matter of fact it's a little less performant, but it's easier to debug and hack.

[ Parent | on HN ]

Re:Analyzing the OpenAPI Tooling Ecosystem by chrisweekly on Thursday September 26, 2024 @10:38PM (#41665745)

Cool beans. Thanks for the response -- TIL!

[meta: IMHO this is an exemplary HN interaction; instead of shouting past each other, we shared very different points of view, and one of us learned something potentially useful.]

Any idea how monstrous migrating from gRPC to ConnectRPC might be, on the backend?

[ Parent | on HN ]

Re:Analyzing the OpenAPI Tooling Ecosystem by cdelsolar on Friday September 27, 2024 @10:33AM (#41670998)

I've never used gRPC before, but from what I can tell, ConnectRPC tries to be compatible with it.

https://connectrpc.com/docs/go/grpc-compatibility/

It might not be super simple. Good interaction, I agree :)

[ Parent | on HN ]

Re:Analyzing the OpenAPI Tooling Ecosystem by bufbuild on Saturday September 28, 2024 @06:48PM (#41683465)

Connect libraries are 100% compatible with gRPC - in many cases, they implement the gRPC spec more faithfully than the core libraries themselves: https://buf.build/blog/grpc-conformance-deep-dive

TLDR: there should be no migration cost.

[ Parent | on HN ]