HomaModule
grpc_homa
Our great sponsors
| HomaModule | grpc_homa | |
|---|---|---|
| 2 | 2 | |
| 166 | 23 | |
| 4.8% | - | |
| 9.3 | 6.3 | |
| 7 days ago | 6 months ago | |
| C | C++ | |
| - | - |
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.
HomaModule
-
Ousterhout: It's time to replace TCP in the Datacenter [pdf]
Homa protocl can be deployed on the basis of existing switches (not all of them, but some of them will play well). See also https://github.com/PlatformLab/HomaModule .
In addition, a closed environment and the SDN's popularity in large data centers is a significant cost-reducing factors compared to typical IPv6 deployment.
-
I just created my first not so basic app in rust! A CLI chat using TCP sockets with Tokio. Anyone willing to do a code review?
Also try doing it with Homa protocol. https://github.com/PlatformLab/HomaModule https://github.com/PlatformLab/grpc_homa
grpc_homa
-
Is It Time to Replace TCP in Data Centers?
This seems like a review of John Ousterhout's work w/ Homa. I highly recommend reading the original. https://arxiv.org/abs/2210.00714
For those who don't know Ousterhout created the first log structured filesystem and created TCL (used heavily in hardware verification but also forming the backbone of the some of the first large web servers: aolserver). I was actually surprised to find out he co-founded a company with the current CTO of Cloudflare. https://en.wikipedia.org/wiki/John_Ousterhout
He has both a candidate replacement as well as benchmarks showing 40% performance improvements with grpc on homa compared to grpc on TCP. https://github.com/PlatformLab/grpc_homa
With that in mind I think nobody will replace TCP and I doubt anything not IP compatible will be able to get off the ground. His argument is essentially that for low latency RPC protocols TCP is a bad choice.
We've already seen people build a number of similar systems on UDP including HTTP replacements that have delivered value for clients doing lots of parallel requests on the WAN.
I think many big tech companies are essentially already choosing to bypass TCP. I recall facebook doing alot of work with memcache on udp. I can't find any public docs on whether or not Google's internal RPC uses TCP.
I wouldn't be surprised at all if in the near future something like grpc/capnproto/twirp/etc had an in-datacenter TCP-free fast path. It would be cool if it was built on Homa.
-
I just created my first not so basic app in rust! A CLI chat using TCP sockets with Tokio. Anyone willing to do a code review?
Also try doing it with Homa protocol. https://github.com/PlatformLab/HomaModule https://github.com/PlatformLab/grpc_homa
What are some alternatives?
efp - A framing protocol bridging the gap between elementary stream data and transport protocols.
gRPC - The C based gRPC (C++, Python, Ruby, Objective-C, PHP, C#)
kcp-cpp - C++ Wrapper around KCP
rust_chat
cppSRTWrapper - Simple C++ wrapper of the SRT protocol for building Server/Client transport solutions
linux - Linux kernel source tree
KCP - :zap: KCP - A Fast and Reliable ARQ Protocol
NATS - High-Performance server for NATS.io, the cloud and edge native messaging system.
srt - Secure, Reliable, Transport