Fasthttp Alternatives

fasthttp reviews and mentions

• Anyone looking for developer to co-work on non-trivial opensource?
  5 projects | reddit.com/r/golang | 1 Feb 2023
• my office want to migrate to go programming language, what framework is recommended between chi or fiber?
  7 projects | reddit.com/r/golang | 2 Jan 2023

  Fiber, while has a lot of batteries included and decent for many use cases, is known for having corner cases (because of internals like fasthttp) like https://github.com/valyala/fasthttp/issues/622

• Ask HN: Slimvoice Alternative?
  13 projects | news.ycombinator.com | 31 Dec 2022
• Mongogram - Social media backend api using golang and mongodb
  5 projects | dev.to | 4 Dec 2022
• Go Framework: No Framework?
  11 projects | news.ycombinator.com | 29 Nov 2022

  "You also get to implement stuff like CSRF protection, cookie signing, anti session fixation, etc. You also lose out on community contributions because you are your own community now."

  In Go, not necessarily, because net/http actually is what many languages would call a "minimalist framework".

  There's a sense in which pretty much everyone here is right. You do need a framework in the general sense; you can't expect to just throw someone a TCP socket and get reasonable work out of them because the web is very complicated nowadays. But the reason why you can "do without a framework" in Go is that it is already a minimal one of its own, and in particular, that "minimality" focuses on providing a mechanism for composing various bits of HTTP code together.

  So, do you need CSRF protection? Go grab this: https://pkg.go.dev/github.com/gorilla/csrf It operates with the integrated net/http Go framework to provide CSRF protection. You are objectively not abandoning the ability to have community-written CSRF protection when you go "frameworkless" in Go. Gorilla in general provides lots of mix-and-match pieces: https://www.gorillatoolkit.org/ , like cookie signing: https://pkg.go.dev/github.com/gorilla/securecookie

  I think calling Go "no framework" is kind of misleading, because I get what you're saying, but the standard library is not the "no framework" option. The "no framework" option is more like using https://github.com/valyala/fasthttp , which is its own server implementation with an incompatible API that does in fact remove you from the community code, other than the code that works only with that server.

  Don't over-read my post. I am merely saying that Go essentially ships with a minimal framework and so it is misleading to say or think of it as being "frameworkless", not that it is mandatory to use it and all other things on top of it are a bad idea. There are times and places to want large, preconfigured packages of additional functionality. But if there are times and places where it is not desirable, Go does come with a minimalist option by default. It is a pretty good, not-very-opionated option suitable for a standard library, where development is slow and there's not much room for experimentation in what a "full" web framework should look like.

  The standard library minimalist framework even makes the other frameworks pluggable. You can, for instance, write an API website, then realize that if you need a conventional HTML website, you can plug in a framework for that part, but leave the API part as-is, simply by routing the API URLs to the existing API code while routing the HTML website to the http.Handler provided by the framework. Even "not using an additional framework" is not the commitment it may be in other environments, because the net/http foundation is still there.

• An interesting process of solving an issue
  2 projects | dev.to | 28 Nov 2022
• FRAMEWORKS IN GOLANG.
  4 projects | dev.to | 1 Nov 2022

  4. fasthttp. The fasthttp framework provides a fast HTTP server and client API which was made as an alternative to net/http due to its limits on optimization opportunities. On current hardware, it can easily handle over 100K qps and over 1M concurrent keep-alive connections thanks to its speed optimization. Additionally, it is designed to use little memory and offers RequestCtx for simple connection upgrade support. Hijack. The Fasthttp API was created with the flexibility to create new client and server implementations from scratch or to extend existing client and server implementations. Documentation Link: https://github.com/valyala/fasthttp

• Source Code Analysis for Go HTTP Framework Hertz
  5 projects | dev.to | 29 Oct 2022

  Hertz was inspired by other open-source frameworks like fasthttp, gin, and echo, in combination with unique challenges faced by ByteDance, Hertz has become production ready and powered ByteDance’s internal services over the years.

• Build REST API with Go Fiber and PlanetScale - Part 1
  3 projects | dev.to | 19 Oct 2022

  Fiber (gofiber.io) is web framework written in Go that much like Express in Nodejs. Fiber have many built in features to build rich web application such as Middleware, API Ready, Template Engine, Websocket support, Rate limiter, etc. They used fasthttp for the engine that claims is the fastest HTTP Engine in Go.

• Go with Chi has more ram consumption and less req/s than Koa or Fastify
  7 projects | reddit.com/r/golang | 3 Oct 2022

  If all you care about is speed and what Go+Chi offers is not enough for you, you should check out fasthttp without any router in between. Be aware of the trade-offs.

• A note from our sponsor - InfluxDB
  www.influxdata.com | 2 Feb 2023

  InfluxDB is the Time Series Platform where developers build real-time applications for analytics, IoT and cloud-native services. Easy to start, it is available in the cloud or on-premises. Learn more →