proposal
natter
| proposal | natter | |
|---|---|---|
| 5 | 1 | |
| 695 | 28 | |
| 2.0% | - | |
| 7.5 | 0.0 | |
| 5 days ago | about 1 year ago | |
| Go | ||
| Apache License 2.0 | MIT License |
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.
proposal
- gRPC Name Resolution & Load Balancing on Kubernetes: Everything you need to know (and probably a bit more)
- Why HTTP/3 is eating the world
-
eBPF will help solve service mesh by getting rid of sidecars
Not convinced that this a better solution then just implementing most of these features as part of the protocol. Most languages already support grpc load balancing.
https://github.com/grpc/proposal/blob/master/A27-xds-global-...
-
Why gRPC for microservices communication?
The future of gRPC load balancing is proxy less using the xDS APIs of Envoy. More info here. But as of now, there is no straightforward solution since there are no xDS management servers supporting this unless you are on GKE where you can use Traffic Director. Istio has experimental support, and it is said that it works, but it might require some manual configuration. If Go is fine for you, you could also be using go-control-plane, but definitely, the ecosystem around gRPC and xDS does not seem to be mature enough.
- Why Load Balancing Grpc Is Tricky
natter
-
Why HTTP/3 is eating the world
I dabbled with QUIC a few years ago and I cannot agree more. It was pleasant to work with, and because it's UDP based, suddenly you can do NAT hole punching more easily.
Funny that you mentioned a VPN, because I make a little experimental project back then to hole punch between two behind-the-NAT machines and deliver traffic between them over QUIC. I was able to make my own L2 and L3 bridge across the WAN, or just port forward from one natted endpoint to an endpoint behind a different NAT.
At one point I used it to L2 bridge my company's network (10.x) to my home network (192.168.x), and I was able to ping my home server from the bridging host. It was quite fun.
Here's the project if anyone is interested: https://github.com/binwiederhier/natter -- it's probably defunct, but it was only experimental anyway.
What are some alternatives?
ngx-grpc - Angular gRPC framework
kill-zscaler - Kill Zscaler without password or jail Zscaler in a virtual machine
quinn - Async-friendly QUIC implementation in Rust
HTTP Parser - http request/response parser for c
vidgear - A High-performance cross-platform Video Processing Python framework powerpacked with unique trailblazing features :fire:
membrane_core - The core of the Membrane Framework, advanced multimedia processing framework
re - Recursive search and replace tool
pixie - Instant Kubernetes-Native Application Observability
erde - Geospatial python toolkit: common functions, easy CLI creation, dataframes streams