grpc-ziti-starter
frpc-go
| grpc-ziti-starter | frpc-go | |
|---|---|---|
| 2 | 7 | |
| 3 | 426 | |
| - | 0.2% | |
| 1.0 | 4.5 | |
| about 1 year ago | 7 days ago | |
| Go | Go | |
| Apache License 2.0 | 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.
grpc-ziti-starter
-
Preferred way of handling/exposing gRPC backends on K8S?
We have a gRPC Project Template which you could use to get started quickly https://github.com/openziti-test-kitchen/grpc-ziti-starter.
- Show HN: Build your gRPC apps with embedded zero trust networking
frpc-go
- ram-dl - A tool to download more RAM written in Go
-
Show HN: RAM-dl – A tool to download more RAM written in Go
3. Calling mkswap, swapon and swapoff, which enables paging out to the block device provided by the NBD client and thus to the connected remote fRPC backend.
Its mostly intended as a tech demo for go-nbd[2] and the WIP r3map[3] library (efficient distributed mmap with mounting and migration support), and just as a fun experiment in general.
[1] https://frpc.io/
-
Announcing Scale: A WebAssembly runtime for running Go functions in any other language
We're currently working on a couple of different projects, but everything we've launched so far (fRPC and Scale) is FOSS.
-
FRPC: A Faster, More Flexible RPC Framework
Hey everyone,
Founder of Loophole Labs here!
The team and I are happy to answer any questions you might have about fRPC, Frisbee, or Loophole in general!
We wrote fRPC because we really liked the DevX and tooling around the proto3 syntax, but we needed the generated code to be significantly more performant than what gRPC provides.
We also needed the ability to extend the RPC framework with other messaging patterns (like pub/sub) and we needed to be able to reuse the underlying TCP connections as required.
Today, fRPC can outperform gRPC by more than 4x, doing more than 2 million RPCs/second on a single node.
You can check out our docs site at https://frpc.io, or check out the repo at https://github.com/loopholelabs/frpc-go
- Extensible and performant proto3-compatible RPC Framework
-
Show HN: FRPC – A Faster, More Flexible RPC Framework
We wrote fRPC because we really liked the DevX and tooling around the proto3 syntax, but we needed the generated code to be significantly more performant than what gRPC provides.
We also needed the ability to extend the RPC framework with other messaging patterns (like pub/sub) and we needed to be able to reuse the underlying TCP connections as required.
There's no way to do this with gRPC (or any other RPC framework that I'm aware of), and so fRPC was born!
As for streaming, it's not only planned (you can check out our roadmap here: https://frpc.io/getting-started/roadmap), but we've already got a PR open for it (https://github.com/loopholelabs/frpc-go/pull/2). Just need to work out a few more bugs before we merge.
What are some alternatives?
inox - 🛡️ A secure web development platform and programming language.
scale - A framework for building high-performance plugin systems into any application, powered by WebAssembly.
fortio - Fortio load testing library, command line tool, advanced echo server and web UI in go (golang). Allows to specify a set query-per-second load and record latency histograms and other useful stats.
hydrapp - Build fast apps that run everywhere with Go and a browser engine of your choice.
grpcurl - Like cURL, but for gRPC: Command-line tool for interacting with gRPC servers
panrpc - Language-, transport- and serialization-agnostic RPC framework with remote closure support that allows exposing and calling functions on both clients and servers.