| boxcar | zzrpc | |
|---|---|---|
| 1 | 2 | |
| 0 | 5 | |
| - | - | |
| 10.0 | 6.1 | |
| almost 2 years ago | 8 months ago | |
| Rust | Rust | |
| GNU Lesser General Public License v3.0 only | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
boxcar
-
Why messaging is much better than REST for inter-microservice communications
I made a very similar project in Rust that seems to mimic this idea: https://github.com/volfco/boxcar
The core idea I had was to decouple the connection from the execution of the RPC. Mats3 looks to be doing a lot more than what I've done so far, but it's nice to see similar ideas out there to take inspiration from.
zzrpc
What are some alternatives?
cadence - Cadence is a distributed, scalable, durable, and highly available orchestration engine to execute asynchronous long-running business logic in a scalable and resilient way.
tonic - A native gRPC client & server implementation with async/await support.
mats3 - Mats3: Message-based Asynchronous Transactional Staged Stateless Services
shmem-ipc - Untrusted IPC with maximum performance and minimum latency. On Rust, on Linux.
ideas2 - Another 85+ Ideas for Computing https://samsquire.github.io/ideas2/
altruistic-angelshark - This project makes automating over one or more Communication Managers easier via OSSI over SSH.
srpc - Simple RPC system based on top of Canary
SocketCluster - Highly scalable realtime pub/sub and RPC framework
Apache Camel - Apache Camel is an open source integration framework that empowers you to quickly and easily integrate various systems consuming or producing data.