Kreya VS grpc-gateway

Looks very nice; I've also given up with Postman. gRPC support would probably get Bruno into my daily workflow immediately. I spent a couple hours in Postman trying to get gRPC to work and could not- the .proto files were never used successfully, and I had better experiences with Kreya [0] and grpcui [1].

[0] https://kreya.app/

Kreya [1] can do that. It is even optimized for it, so that diffs should be perfectly readable.

[1] https://kreya.app

As one of the creators, I can recommmend https://kreya.app. It is not open source (like Postman), but has a strong focus on privacy and also stores the data locally.

As it has more powerful features (IMO) than most alternatives listed here, I am a little disappointed that it isn't mentioned more often.

There is also https://kreya.app, which has more features, but is closed-source

Given the recent update[0] pushed by the Insomnia team I am now looking for alternatives.

For now the best alternative I've found is Bruno[1]. But sadly it does not support gRPC.

Does anyone have a better solution?

These are some options I've looked into:

- https://hoppscotch.io/

- https://hurl.dev/

- https://recipeui.com/

- https://kreya.app/

- https://github.com/flawiddsouza/Restfox

[0] - https://github.com/Kong/insomnia/issues/6585

[1] - https://github.com/usebruno/bruno

If you need gRPC, I can recommend https://kreya.app/

I like Kreya (kreya.app), but I am biased, since I am one of the creators :)

Have you tried Kreya? While it does not support all of the many features of Postman, it has some innovative features. While also being web-based, it uses the native WebView of the OS, resulting in less RAM-usage than Electron based apps.

it lacks flexibility but i really enjoy grpc-gateway for 99% of my work

https://github.com/grpc-ecosystem/grpc-gateway

gRPC Gateway is a protoc plugin that reads gRPC service definitions and generates a reverse proxy server that translates a RESTful JSON API into gRPC.

I don't have any example that's public atm, but the guide in grpc-gateway is pretty clear/can be followed step by step.

https://github.com/grpc-ecosystem/grpc-gateway

To integrate with Fiber, I used the Fiber Adaptor (also pretty straightforward): https://docs.gofiber.io/api/middleware/adaptor

I wonder if they would be happy with something like this: https://github.com/grpc-ecosystem/grpc-gateway

Protobuf is used is massively scaled services like firebase. But you'll still see JSON in streamed realtime services like AWS Kinesis. Hopefully google had a return on investment for creating and using this protocol, but it's not hard to prove that it's far from essential. Out of apparent convenience I use grpc-gateway so I can expose both Protobuf and JSON, but honestly I wouldn't do it again

GRPC is an alternative to rest, rest and GRPC both use the http protocol. But you won’t be able to use fetch to call a GRPC endpoint, you should look into setting up a GRPC proxy within the application(hopping you have access to the source code) grpc-gateway. If you don’t have access you’ll have to create a new container that proxies the calls

(There is an option called google.api.http, that lets you set up a URL that can be used to make HTTP/1 REST requests, which get translated to gRPC calls if you're using grpc-gateway as a proxy in front of your service. That has nothing to do with the requests that are made by gRPC clients and servers themselves.)

Have you looked at https://github.com/grpc-ecosystem/grpc-gateway ?

protoc-gen-grpc-gateway — plugin for creating a gRPC REST API gateway. It allows gRPC endpoints as REST API endpoints and performs the translation from JSON to proto. Basically, you define a gRPC service with some custom annotations and it makes those gRPC methods accessible via REST using JSON requests.