Show HN: Ezy – open-source gRPC client, alternative to Postman and Insomnia
155 points| notmedia | 3 years ago |github.com
- Full support of shortcuts - Reworked collections management - Notifications - Improved UX
gRPC clients I’ve worked with had drawbacks and didn’t fit my use-case in a way I was expecting, since I’ve started working with gRPC 3+ years ago.
Since then, I wanted a tool that fits any need in gRPC world. This is why I created ezy.
Compared to Insomnia and Postman, ezy offers better streams support, allows you to use Server-Side and Mutual TLS with custom TLS certificates, works with gRPC-Web and has a more slick UI/UX.
If you are looking for a gRPC/gRPC-Web client which fits your needs, give ezy a chance!
I’d love to hear your feedback and answer any questions regarding ezy.
atombender|3 years ago
Some feedback after 5 minutes of testing:
* It doesn't remember your "environment". So if I call endpoint A and then click on endpoint B to try that, it forgets which environment is being targeted.
* Similarly, metadata is also specific to the request. If you use metadata for providing authorization headers, that means you have to enter the metadata separately every time you make a different request; there's no way to share metadata as an "environment".
* If you create a collection and click "Create", and it errors saying an imported proto resource wasn't found, the entire collection disappears.
* The app uses the proto schema to show a list of endpoints, but it doesn't know anything about the message and response schemas, and you can't browse the types? It seems tedious to have to manually enter the request as a JSON payload.
* Similarly, response is shown in JSON, rather than Proto data. So I can't see what the returned types actually are.
* The "Request" and "Metadata" editors are super laggy to the point of being unusable. It takes several seconds for what I type to appear in the editor, and my computer's CPU usage goes to 150% while it's sitting there doing nothing. Is there some kind of autocompletion that's supposed to kick in that's going into overdrive?
* Clicking on an endpoint adds another tab. Click around and you end up with dozens of tabs. Seems a bit pointless.
* No support for setting HTTP headers or seeing the returned headers.
unknown|3 years ago
[deleted]
notmedia|3 years ago
> It doesn't remember your "environment". So if I call endpoint A and then click on endpoint B to try that, it forgets which environment is being targeted. Similarly, metadata is also specific to the request. If you use metadata for providing authorization headers, that means you have to enter the metadata separately every time you make a different request; there's no way to share metadata as an "environment".
Yeah, I have this in plans for taking environment and Metadata from previous tab - https://github.com/getezy/ezy/issues/30
> If you create a collection and click "Create", and it errors saying an imported proto resource wasn't found, the entire collection disappears.
Ha, interesting case, you selected the file and then just delete it before clicking create :) I will think how to handle this.
> The app uses the proto schema to show a list of endpoints, but it doesn't know anything about the message and response schemas, and you can't browse the types? It seems tedious to have to manually enter the request as a JSON payload.
This is the great point, was already mentioned earlier, I have plans to add auto-mocking feature for request payloads and autocompletion in code editor this will fix this issue. Also I will think for option to show raw Protobuf definitions
> Similarly, response is shown in JSON, rather than Proto data. So I can't see what the returned types actually are.
Maybe you have an idea on how we can represent decoded message (which an object) and map it to Protobuf Message definition?
> The "Request" and "Metadata" editors are super laggy to the point of being unusable. It takes several seconds for what I type to appear in the editor, and my computer's CPU usage goes to 150% while it's sitting there doing nothing. Is there some kind of autocompletion that's supposed to kick in that's going into overdrive?
Interesting, this is the first feedback about app performance. Can you open an issue and put more details there? I need to know app version, your OS, how much tabs opened and how much are you typing. Will be helpfull, but I try to reproduce it anyway.
> Clicking on an endpoint adds another tab. Click around and you end up with dozens of tabs. Seems a bit pointless.
Sorry, I can't reproduce this bug. You said clicking around, where exactly I need to click?
> No support for setting HTTP headers or seeing the returned headers.
You can set it in your Metadata and this should work as expected.
ushakov|3 years ago
BloomRPC looked ugly and outdated, Kreya would crash on my M1 mac and Insomnia didn’t have all the features I needed. Ezy was a new discovery and offered both great UX and features that were missing from other clients
When I’m working with gRPC APIs, Ezy is the client I reach out to!
notmedia|3 years ago
wdb|3 years ago
notmedia|3 years ago
Tested it with common gRPC cases. Just some things why it's not good for gRPC:
HatchedLake721|3 years ago
codetrotter|3 years ago
Does the TLS/mTLS settings allow you to override the host name of the server, so that I can connect to localhost even though the cert CN is example.com?
Is it able to import proto files to define endpoints automatically, and to fill in generated data for the types?
notmedia|3 years ago
> Does the TLS/mTLS settings allow you to override the host name of the server, so that I can connect to localhost even though the cert CN is example.com?
Yes, in TLS settings you can override SSL target name for this cases.
> Is it able to import protobuf files to define endpoints automatically, and to fill in generated data for the types?
When you importing the protobuf files ezy parse them and generate to you collection of all existing services and methods. I have plans to add auto-mocking feature, which will generate prefilled values for the request payload, stay tuned!
topicseed|3 years ago
notmedia|3 years ago
arein3|3 years ago
notmedia|3 years ago
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.
hankchinaski|3 years ago
bob2047|3 years ago
mxuribe|3 years ago
kermire|3 years ago
Disclaimer: I'm the maintainer for it.
notmedia|3 years ago
unknown|3 years ago
[deleted]
inshadows|3 years ago
[deleted]