Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What is the difference between WIT and WRPC? #666

Open
ashishsinghin opened this issue Feb 18, 2025 · 1 comment
Open

What is the difference between WIT and WRPC? #666

ashishsinghin opened this issue Feb 18, 2025 · 1 comment

Comments

@ashishsinghin
Copy link

Hi everyone,

I'm currently exploring different technologies and came across both WIT and WRPC, but I’m not entirely sure about the key differences between the two. Could anyone please provide some insights on:

  1. What exactly distinguishes WIT from WRPC?
  2. In what scenarios might one be preferred over the other?
  3. Are there specific use cases or performance benefits associated with either?

I’d appreciate any detailed comparisons or documentation that can help clarify these differences.

Thanks in advance!

@rvolosatovs
Copy link
Member

WIT and wRPC aren't really comparable, since wRPC uses WIT. (Although it potentially could use other IDLs as well)

The best example, perhaps, would be gRPC. gRPC uses protocol buffers to define services and data models and uses HTTP/2 as the transport.
wRPC uses WIT to define services and data models and uses TCP/QUIC/NATS.io/Unix sockets/anything else as the transport.

That said, instead of WIT, one could potentially use protocol buffers or e.g. OpenAPI to define services and data models - wRPC could still send them, since WIT is a superset of these technologies.

It seems that you might want to compare wRPC to gRPC or WIT to protocol buffers instead?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants