Hacker News new | ask | show | jobs
by arein3 1287 days ago
Best grpc client is to not use grpc. Better use json over http2 (and enable compression if needed).
1 comments

Hey! I think it's really depends on your needs and expectations from protocol you choose.

gRPC is not a silver bullet, but it offers you structure via protobuf messages and automatically generated clients for most used languages. Not in all places in your architecture you need to use high-performance protocols. It's a trade-off and only you decide whats better in concrete section.

The problem which ezy solves - gRPC is popular, and yes, maybe we have faster protocols, but a lot of developers using it and this tool just help them to work with it.

gRPC has been a pain (customization of the generated clients, automation testing, even usual testing). I haven't heard of Ezy (used BloomRPC, insomnia, and another client, all of them were an incomplete solution). I will be sure to check Ezy next time I have to use gRPC.

Some of the features I couldnt find on the gRPC apps I tried were: 1) the ability to have complete information about the request and the response, and also I couldn't add headers to the grpc request. 2) the ability to automate (run the requests without a GUI), the way newman works for postman.

I just wish gRPC would not be used on any new projects and people would use more sensible solutions.

For automating gRPC tests you can use Step CI

Disclosure: I'm the author

https://docs.stepci.com/guides/testing-grpc.html

> the ability to have complete information about the request and the response

Can you describe what information you want to see?

> the ability to automate (run the requests without a GUI)

Yeah, this is my goal - I want to add tests support to ezy with ability to run them on CI/CD

>Can you describe what information you want to see?

Everything there could be (of course maybe in a separate expander). I needed the request/response headers, but maybe somebody could need something even more up the stack (ex. if the connexion was reused or a new one was created).

Also don't know if this is already implemented, but I think the option to generate a curl command for the request should be possible, since curl supports http2.