What is Mercury?
A modular JSON-RPC library that allows pluggable transport layers, JSON libraries, and effect/async monads. It is used to communicate with embedded devices where the device is acting in the server role.
Mercury is a tool in the Remote Procedure Call (RPC) category of a tech stack.
Mercury is an open source tool with GitHub stars and GitHub forks. Here’s a link to Mercury's open source repository on GitHub
Why developers like Mercury?
Here’s a list of reasons why companies and developers use Mercury
Be the first to leave a pro
- Free and open source license
- Allow for swappable transports
- Allow for swappable JSON libraries
- Be usable without code generation
Mercury Alternatives & Comparisons
What are some alternatives to Mercury?
gRPC is a modern open source high performance RPC framework that can run in any environment. It can efficiently connect services in and across data centers with pluggable support for load balancing, tracing, health checking...
It is a very simple protocol, defining only a few data types and commands. It allows for notifications (data sent to the server that does not require a response) and for multiple calls to be sent to the server which may be answered out of order.
It is a high-performance, light weight, java based RPC framework. Dubbo offers three key functionalities, which include interface based remote call, fault tolerance & load balancing, and automatic service registration & discovery.
No related comparisons found