How does the `net/http` package handle concurrency?

The standard net/http server inherently creates a new goroutine for every incoming HTTP connection.

This makes writing HTTP handlers in Go incredibly simple, as you write synchronous, blocking code. The scheduler multiplexes these thousands of goroutines effortlessly. However, because each handler is concurrent, any shared state (like a cache map or database connection) accessed inside a handler MUST be protected by Mutexes or channels.