Our great sponsors
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
waggy
The dead simple, easy-to-use library for writing HTTP handlers and routers in Go that can be used in standard HTTP server environments or in WAGI (Web Assembly Gateway Interface) environments
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
I use Fiber. It's pretty good, simple, based on middlewares.
Assuming you mean “frameworks” to mean frameworks for APIs, then no. Just stdlib and gorilla/mux for me.
Assuming you mean “frameworks” to mean frameworks for APIs, then no. Just stdlib and gorilla/mux for me.
If I started working at a Go shop that used a framework, I would hope it would be Fiber. Not for any particular solid reasons, though. Rather just personal preference based on how the developer experience feels to me personally.
With the rising popularity of WASM, I’d probably use something like wazero coupled with the library I just wrote and released, waggy for writing the individual handlers for each route, though.
With the rising popularity of WASM, I’d probably use something like wazero coupled with the library I just wrote and released, waggy for writing the individual handlers for each route, though.
I am learning Go. I find confusing this discussion about web frameworks deviation from the standard library, however I've read about chi library as a good alternative, what do you think?