gloo
gloo
Our great sponsors
| gloo | gloo | |
|---|---|---|
| 3 | 2 | |
| 3,980 | 1,138 | |
| 0.8% | 1.8% | |
| 9.5 | 8.1 | |
| 4 days ago | 12 days ago | |
| Go | C++ | |
| Apache License 2.0 | GNU General Public License v3.0 or later |
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.
gloo
-
How to choose the best versioning mechanism?
A similar approach can be seen here: solo.io/gloo
-
Releasing Gloo 0.4.0
Does it bug anyone else when people come out promoting their "new" thing that has used the name of an existing well established thing? https://github.com/solo-io/gloo like... how hard is it to search and see the name's already taken?
-
Monthly Who Is Hiring
We are a small but rapidly growing startup developing cutting edge Service Mesh and API Gateway solutions for a sizable list of production customers. We are known in the community for our open source API Gateway and service mesh management plane as well as our enterprise product offerings.
gloo
-
Releasing Gloo 0.4.0
These are two separate libraries that do very different things but share the same name. They are also written in two separate languages. That is a sizable gap between them, and reusing names happens often with libraries. Gloo (rust-wasm, this post) is also not new. Though, relative to Gloo (Go, solo-io), it is newer. But, there is also a Github repo even older than Gloo (solo-io): https://github.com/facebookincubator/gloo. As well, even if these were for some odd reason all about wasm, none of them are actually that popular. solo-io Gloo has the most stars (though that isn't the best metric of popularity, since it is relative to the community that actually uses it), but 3k simply isn't that much. There is certainly a good argument to look down on libraries that reuse popular library names, but this isn't really the case here. Both started not too long after each other (solo-io would not have most of the stars it currently has when Gloo-Rust started), are in separate languages (thus separate communities), and do very separate things.
-
Distributed Training Made Easy with PyTorch-Ignite
backends from native torch distributed configuration: nccl, gloo, mpi.
What are some alternatives?
emissary - open source Kubernetes-native API gateway for microservices built on the Envoy Proxy
NCCL - Optimized primitives for collective multi-GPU communication
apisix - The Cloud-Native API Gateway
ompi - Open MPI main development repository
grpc-health-probe - A command-line tool to perform health-checks for gRPC applications in Kubernetes and elsewhere
idist-snippets
Kong - 🦍 The Cloud-Native API Gateway and AI Gateway.
why-ignite - Why should we use PyTorch-Ignite ?
opa-envoy-plugin - A plugin to enforce OPA policies with Envoy
xla - Enabling PyTorch on XLA Devices (e.g. Google TPU)
mizu - The API traffic viewer for Kubernetes providing deep visibility into all API traffic and payloads going in, out and across containers and pods inside a Kubernetes cluster. Think TCPDump and Wireshark re-invented for Kubernetes [Moved to: https://github.com/kubeshark/kubeshark]
ignite - High-level library to help with training and evaluating neural networks in PyTorch flexibly and transparently.