sigma
a small wrapper around go-chi HTTP router. (by twiny)
connect-go
Moved to https://github.com/connectrpc/connect-go (by bufbuild)
| sigma | connect-go | |
|---|---|---|
| 2 | 26 | |
| 8 | 3 | |
| - | - | |
| 2.6 | 0.0 | |
| 7 months ago | 8 months ago | |
| Go | Go | |
| MIT License | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
sigma
Posts with mentions or reviews of sigma.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-11-01.
-
Which framework do you use for api and frontend?
i like using: go-chi/chi its minimal & compatible with the standard net/http. I've wort a small wrapper for it exposing minimal API https://github.com/twiny/sigma
-
Chi , gin , mux , fiber or standard library ?
for me I like go-chi is good, lightweight and compatible with go net/http. i've written a small wrapper around it exporting minimal API. https://github.com/twiny/sigma I also use echo v4 on couple of project it is good - but you must use their standards. the echo.Context...etc
connect-go
Posts with mentions or reviews of connect-go.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-05-29.
- Code generation for REST inter service communication?
-
Flutter + gRPC for Desktop and Mobile App Development - Good choice?
In my opinion it's a good idea, it's the architecture we use at work, and it works well for us. The main limitation to be aware of is that many PaaS don't support gRPC traffic (because of the proxies used). For example, DigitalOcean App Platform or Heroku if I remember correctly. If the way you want to host your backend is OK with HTTP/2 and gRPC traffic, then it's not a limitation. One way around this limitation is to use the gRPC-Web protocol, or the Connect protocol (https://connect.build/). Unfortunately, Dart's gRPC client does not support the gRPC-Web protocol outside the web platform. So for a mobile application, it's not usable at the moment. (If this PR were accepted, it would solve the issue: https://github.com/grpc/grpc-dart/pull/557.) As for Connect, no client is currently offered by Buf for Dart. Don't hesitate if you want to know more. That said, I'd advise you to use the Connect implementation for Go to implement your backend. Connect will enable your server to speak all three protocols (gRPC, gRPC-Web and Connect), which is very useful in the long term. What's more, the code is cleaner, and you benefit from official support for observability with OpenTelemetry. If you don't know Buf (the creators of Connect),I suggest you visit their website: https://buf.build/. :-) Good luck!
- How do I provide bot RPC and REST endpoints?
-
Building a modern gRPC-powered microservice using Node.js, Typescript, and Connect
As mentioned in the intro, we are going to use Buf and Connect as our tools. We’ll start by installing the dependencies.
- Ask HN: Is it possible to compile TypeScript to Golang?
-
gRPC + Envoy + grpc-web = scalable multiplexed streaming?
Its annoying, because the rest of Connect (https://connect.build/) looks really really cool. But its no good for me in a complex app if I can't have multiple streams from the server :/
-
Issues with proxying gRPC services to web, and a potential prototype
Consider checking out https://connect.build from https://buf.build. Supports a simpler protocol than grpc-web. Includes a js/ts client for frontend. Then you don’t necessarily need a rest layer, but could leverage the proxy your building.
-
Best Web Sever Framework?
Twirp (though I'd move to https://connect.build for my next project) to do JSON based RPC using protobufs.
-
GRPC Gateway API Client?
my backend is go via https://github.com/bufbuild/connect-go , it's stable and all open source. just try and test it for your purpose. my project run all in 300 server more....
- Connect – A Better gRPC
What are some alternatives?
When comparing sigma and connect-go you can also consider the following projects:
goblin - A golang http router based on trie tree.
grpc-go - The Go language implementation of gRPC. HTTP/2 based RPC
Iris - The fastest HTTP/2 Go Web Framework. New, modern and easy to learn. Fast development with Code you control. Unbeatable cost-performance ratio :rocket:
grpc-gateway - gRPC to JSON proxy generator following the gRPC HTTP spec
groundup
protobuf-es - Protocol Buffers for ECMAScript. The only JavaScript Protobuf library that is fully-compliant with Protobuf conformance tests.
mir - Mir is a toolkit for register method handler to http engine router(eg: gin,echo,iris,mux,httprouter) use struct tag info.
twirp - A simple RPC framework with protobuf service definitions
nchi - golang http router with elegance, speed, and flexibility
examples-go - An example Go server built with Connect.
drpc - drpc is a lightweight, drop-in replacement for gRPC
gRPC - The C based gRPC (C++, Python, Ruby, Objective-C, PHP, C#)