🤗 [Question]: Does Fiber handle each request in different goroutines? about fiber HOT 2 CLOSED

Fiber, built on top of the fasthttp package, does indeed handle each request in a separate goroutine by default. This means that when a new request arrives, Fiber spawns a new goroutine to handle it. However, Fiber utilizes an efficient goroutine pool to manage these goroutines, ensuring that the overhead of goroutine creation is minimized.

Regarding the maximum number of concurrent goroutines, it's influenced by various factors including system resources and configuration settings. Neither Fiber nor fasthttp imposes a specific limit on the number of concurrent goroutines. Instead, it relies on the underlying Go runtime to manage goroutines efficiently.

These characteristics are specific to Fiber and are derived from its underlying fasthttp package, which is known for its lightweight and high-performance nature in handling HTTP requests in Go applications.

from fiber.

@ReneWerner87
Thank you very much! I understand.

from fiber.