connect-go VS openapi-generator-cli

In my opinion it's a good idea, it's the architecture we use at work, and it works well for us. The main limitation to be aware of is that many PaaS don't support gRPC traffic (because of the proxies used). For example, DigitalOcean App Platform or Heroku if I remember correctly. If the way you want to host your backend is OK with HTTP/2 and gRPC traffic, then it's not a limitation. One way around this limitation is to use the gRPC-Web protocol, or the Connect protocol (https://connect.build/). Unfortunately, Dart's gRPC client does not support the gRPC-Web protocol outside the web platform. So for a mobile application, it's not usable at the moment. (If this PR were accepted, it would solve the issue: https://github.com/grpc/grpc-dart/pull/557.) As for Connect, no client is currently offered by Buf for Dart. Don't hesitate if you want to know more. That said, I'd advise you to use the Connect implementation for Go to implement your backend. Connect will enable your server to speak all three protocols (gRPC, gRPC-Web and Connect), which is very useful in the long term. What's more, the code is cleaner, and you benefit from official support for observability with OpenTelemetry. If you don't know Buf (the creators of Connect),I suggest you visit their website: https://buf.build/. :-) Good luck!

As mentioned in the intro, we are going to use Buf and Connect as our tools. We’ll start by installing the dependencies.

Its annoying, because the rest of Connect (https://connect.build/) looks really really cool. But its no good for me in a complex app if I can't have multiple streams from the server :/

Consider checking out https://connect.build from https://buf.build. Supports a simpler protocol than grpc-web. Includes a js/ts client for frontend. Then you don’t necessarily need a rest layer, but could leverage the proxy your building.

Twirp (though I'd move to https://connect.build for my next project) to do JSON based RPC using protobufs.

my backend is go via https://github.com/bufbuild/connect-go , it's stable and all open source. just try and test it for your purpose. my project run all in 300 server more....

Hi, I want to create my dto's from a bundle file. This works nearly good, I just don't need all the functions which I am getting. I only need the model structs. I am currently using https://github.com/OpenAPITools/openapi-generator-cli via docker and I am passing the bundle.yml inside. I have the following parameter to only get model files:

You can generate boilerplate code stubs with OpenAPI spec. Yes! you heard it right! you only need to write the business logic that’s all, everything will be generated for you. There are so many generators available for every programming language. Find it here https://openapi-generator.tech. GitHub repo for the same https://github.com/OpenAPITools/openapi-generator & https://github.com/OpenAPITools/openapi-generator-cli

- https://github.com/OpenAPITools/openapi-generator-cli

OAG is a Java project that uses Mustache templates to configure each supported programming language. It provides a CLI openapi-generator-cli that will download the appropriate JAR file and invoke the java executable to run OAG.

So I'm assuming you're talking about generating Rust types from TypeScript? If you can get your typescript definitions into OpenAPI (i.e, via typeconv) you can use the openapi generator cli to generate rust types. However this is geared towards web backends rather than pure IPC or cross-lang interop.

https://github.com/OpenAPITools/openapi-generator-cli I didn't build it so you may need to do some research on it

openapi-generator-cli is what I use for openapi/swagger, along with the nestjs swagger plugin. it's not perfect but it gets the job done.

The OpenAPI generator configuration file. See Configuration for more info.