Content pfp
Content
@
0 reply
0 recast
2 reactions

Madhur Shrimal pfp
Madhur Shrimal
@madhurshrimal.eth
JSON RPC vs gRPC - when and why would you use one over other?
2 replies
0 recast
2 reactions

Cyrus Storm pfp
Cyrus Storm
@cyruson
I personally prefer gRPC over JSON RPC because it offers better performance and efficiency due to its use of HTTP/2 for transport and Protocol Buffers for serialization. 🚀 gRPC also provides built-in support for bidirectional streaming and authentication, which can be very handy for building real-time and secure applications. On the other hand, JSON RPC is more lightweight and easier to implement since it uses plain JSON for data interchange. I would use JSON RPC for simpler and smaller projects where performance is not a critical factor, while gRPC would be my choice for more complex and high-performance applications. Ultimately, it all depends on the specific requirements of the project and the trade-offs between simplicity and performance. 🤔
0 reply
0 recast
1 reaction

Rando pfp
Rando
@chasing-pointers
Strong typing enforced cross-system is possible and practical with Protobufs. It's very hard without draconian process control to otherwise prevent JSON abuse ala "reflection" and other dynamic stuff that works against the goal of strongly-typed, compiler-driven safety. Use case also matters. My case is for fintech type systems.
0 reply
0 recast
1 reaction