DEV Community

Cover image for Welcome to Fiber — an Express.js styled web framework written in Go with ️
Vic Shóstak
Vic Shóstak

Posted on • Updated on

Welcome to Fiber — an Express.js styled web framework written in Go with ️


Hello, World! 👋 Today we will deal with a young (but ambitious) Fiber web framework on Go and understand that this is not "yet another new framework, like X", but a great tool for creating rapid web applications.

📌 It will be a review article, dive into Fiber we will start further.

Table of contents

  1. What is Fiber and why is it so good?
  2. Useful information to start working with Fiber
  3. Main features
  4. Benchmarks
  5. Project assistance

What is Fiber and why is it so good?

Follow official README from GitHub repository:

Fiber is an Express.js styled HTTP web framework implementation running on Fasthttp, the fastest HTTP engine for Go (Golang). The package make use of similar framework convention as they are in Express.

And I tend to agree with that. If you have ever implemented a web application on Node.js using Express.js (like me), then many methods and principles will seem very common to you!

For example, this is standard Hello, World! by Express.js:

// ...

const app = express()

app.get('/', (req, res) => res.send('Hello, World!'))

Enter fullscreen mode Exit fullscreen mode

And similar example by Fiber:

// ...

app := fiber.New()

app.Get("/", func(c *fiber.Ctx) {
  c.Send("Hello, World!")

Enter fullscreen mode Exit fullscreen mode

Useful information to start working with Fiber

Actually, all you need for start is official documentation! 😉

Fiber, as a web framework, was created with idea of minimalism to more easily start creating a web application's backend for new gophers, but who have experience with JavaScript.

That's what the authors themselves say:

People switching from Node.js to Go often end up in a bad learning curve to start building their webapps, this project is meant to ease things up for fast development, but with zero memory allocation and performance in mind.

main features

Main features

  • Optimized for speed and low memory usage
  • Rapid Server-Side Programming
  • Easy routing with parameters
  • Static files with custom prefix
  • Middleware with Next() support
  • Express API endpoints
  • Extended documentation

Easy to enable the prefork feature

Just set Prefork to true on your code:

// ...

app := fiber.New()

app.Prefork = true // enable prefork

app.Get("/", func(c *fiber.Ctx) {
  c.Send(fmt.Sprintf("Hi, I'm worker #%v", os.Getpid()))
  // => Hi, I'm worker #16858
  // => Hi, I'm worker #16877
  // => Hi, I'm worker #16895

Enter fullscreen mode Exit fullscreen mode

What's prefork?

Enable prefork feature will spawn multiple go processes listening on the same port. Nginx has a great article about Socket Sharding, this picture are taken from the same article 👇


✨ My favorite killer feature ✨

And one more big feature (for me) is full access to all Fasthttp methods and properties (read documentation for more info about it).

Yeah, you didn't mishear! Fiber is extremely easy to use as Express.js and has everything under the hood that Fasthttp has now and will have in the future 🔥

Benchmarks 🤖

Click here to see all benchmark results. I'll only bring some.

  • TechEmpower: JSON serialization

JSON serialization

  • Go-Web: enable HTTP pipelining

enable http pipelining

Project assistance

  1. Add a GitHub Star to project.
  2. Tweet about project on your Twitter.
  3. Help to translate README and API Docs to another language.

Photo by

[Title] Fiber Authors
[1] Nate Grant


If you want more articles (like this) on this blog, then post a comment below and subscribe to me. Thanks! 😻

And of course, you can help me make developers' lives even better! Just connect to one of my projects as a contributor. It's easy!

My projects that need your help (and stars) 👇

  • 🔥 gowebly: A next-generation CLI tool for easily build amazing web applications with Go on the backend, using htmx & hyperscript and the most popular atomic/utility-first CSS frameworks on the frontend.
  • create-go-app: Create a new production-ready project with Go backend, frontend and deploy automation by running one CLI command.
  • 🏃 yatr: Yet Another Task Runner allows you to organize and automate your routine operations that you normally do in Makefile (or else) for each project.
  • 📚 gosl: The Go Snippet Library provides snippets collection for working with routine operations in your Go programs with a super user-friendly API and the most efficient performance.
  • 🏄‍♂️ csv2api: The parser reads the CSV file with the raw data, filters the records, identifies fields to be changed, and sends a request to update the data to the specified endpoint of your REST API.
  • 🚴 json2csv: The parser can read given folder with JSON files, filtering and qualifying input data with intent & stop words dictionaries and save results to CSV files by given chunk size.

Top comments (17)

inerkyjad profile image
Hassan Aoutof

@koddr , i do very much like the idea of the framework and i would love to rewrite a slow Fastify project in it, ofc i'll first have to verify the claims being made and play with it myself and maybe even become a member of the community, but i'm getting skeptical because i see @kataras comments were hidden by you, did he have something bad to say about the framework ?? in general hiding comment's is bad and it doesn't inspire confidence nor trust. why was his comment hidden ?!

koddr profile image
Vic Shóstak

Nothing wrong there, he just fixed an old bug, which he posted in the comments. That's all.

Exposed his comments, since it's so shocking to some of my readers, no problem.

inerkyjad profile image
Hassan Aoutof

Thank you, i gave the project a GitHub star already because it doesn't matter if it has some bugs, that's fixable the important thing is the idea, and i'll start trying out soon.

kataras profile image
Gerasimos (Makis) Maropoulos • Edited

Based on I should be able to register a route of: app.Get("/api/values/:id", func(ctx *fiber.Ctx) but it can't even do that.... it panics

Anyway, I fixed it with PR:

Screenshot with my PR

Good luck to this initiative! Please inform your users that this framework does not support HTTP/2.

Gerasimos Maropoulos. Author of the Iris web framework.

koddr profile image
Vic Shóstak • Edited

Yes, framework is too young and have some trouble (its written by one man as side project... not me, but I active help to promote).

Thx for PR :D

P.S. btw, I'm really looking forward to the Iris CLI release ;)

kataras profile image
Gerasimos (Makis) Maropoulos • Edited

Vic you are koddr! Oh my god good job mate I hope my projects gave you an idea about how the whole thing works, good luck and anytime you need my help you have it!

P.S I am working on it as we speak, I found the bug when I was iris-cli benchmark of fiber to test its performance :)

Thread Thread
koddr profile image
Vic Shóstak

Yes, my friend, it's me 🥰

Thx for this words, it's extremely important for me (really, thank you).

P.S. actually, your first commit of Iris CLI (yep, I seen this moment) gave me an idea for Create Go App. It's something like CRA (create-react-app), but for every Go web frameworks... ONE CLI TO RULE THEM ALL! haha 🤗

P.P.S. I'm not sure, what gophers have to say, but I personally need similar all-in-one solution (both hyped frontend/backend frameworks and configured Docker containers by one CLI command)... and why not to write it by myself 😉

davidmz profile image
Давид Мзареулян • Edited

Why do we need prefork in Go? Isn't regular gorutines enough?

kataras profile image
Info Comment hidden by post author - thread only accessible via permalink
Gerasimos (Makis) Maropoulos • Edited

In short, prefork is done through Unix' SO_REUSEADDR and it does not work on Windows hosts. You can implement preforking on any web framework, including the standard net/http. A good library (that iris uses too) is tcplisten by @valyala the creator of fasthttp and a good friend. Example code:

 listenerCfg := tcplisten.Config{
    ReusePort:   true,
    DeferAccept: true,
    FastOpen:    true,

for i:=0;i<runtime.NumCPU();i++ {

    /* 1. inline servers, share the same binary.
    ln, err := listenerCfg.NewListener("tcp4", ":8080")
    if err != nil {
    go http.Serve(ln, yourMux_Router)

    /*2. Start the same binary with an argument of `--prefork`
         or anything that will mark the server as a fork. 
        and finally:


http.ListenAndServe(":8080", yourMux_Router) // blocks. 

Also, see the discussion at the fasthttp repository itself:

I noticed that you recently removed the prefork method from your TechEmpower
benchmark code. Do you no longer believe the prefork method to offer better performance? by @manthedan at

fenny profile image

Preforking is making use of multiple socket listeners on OS level. We explained preforking with images in our docs

davidmz profile image
Давид Мзареулян

Does prefork mean that workers are executed in different processes (not goroutines) and cannot communicate or share memory with each other?

Thread Thread
fenny profile image
Fenny • Edited

This is correct, preforking is for specific use cases. If you work with an external database it should be no problem, because you can pool connections. You can see a good result here:

ben_schoeffmann profile image
Benedikt Schöffmann

Hey Vic,

thanks for this article! I wanted to dive into Go for a long time, this is the kick in the butt I needed :)


P.S.: My first ever posting.

koddr profile image
Vic Shóstak

This is very cool! Glad I could move you.

orenmizr profile image
Oren Mizrahi

How is it compared to expressJS - connections benchmarks-wise ? (i'm sure it is better, but how much better)

fenny profile image
Fenny • Edited

Plaintext responses per second
Fiber - 6,114,300/s (0 errors) 0.5ms avg latency
Express - 261,708/s (59 errors) 608.9ms avg latency

JSON responses per second
Fiber - 1,212,833/s (0 errors) 0.1ms avg latency
Express - 244,061/s (0 errors) 1.1ms avg latency

20 database queries per request
Fiber - 19,757/s (0 errors) 25.6ms avg latency
Express - 4,259/s (0 errors) 118.4ms avg latency

Keep in mind that these benchmarks are 1 month old and fiber is being updated on a daily basis. Fiber v1.8 will have better performance.

I will update this comment when techempower tested v1.8.

josephmbassey profile image
Joseph Michael

This is awesome, coming from a nodejs/expressjs background, will make it easy to understand and use Go. 👍

Some comments have been hidden by the post's author - find out more