Database connection best practice

I've an app that uses net/http. I register some handlers with http that need to fetch some stuff from a database before we can proceed to writing the response and be done with the request.

My question is in about which the best pratice is to connect to this database. I want this to work at one request per minute or 10 request per second.

I could connect to database within each handler every time a request comes in. (This would spawn a connection to mysql for each request?)

package main

import (
    "database/sql"
    _ "github.com/go-sql-driver/mysql"
    "net/http"
    "fmt"
)

func main() {

    http.HandleFunc("/",func(w http.ResponseWriter, r *http.Request) {
        db, err := sql.Open("mysql","dsn....")
        if err != nil {
            panic(err)
        }
        defer db.Close()

        row := db.QueryRow("select...")
        // scan row

        fmt.Fprintf(w,"text from database")
    })

    http.ListenAndServe(":8080",nil)
}

I could connect to database at app start. Whenever I need to use the database I Ping it and if it's closed I reconnect to it. If it's not closed I continue and use it.

package main

import (
    "database/sql"
    _ "github.com/go-sql-driver/mysql"
    "net/http"
    "fmt"
    "sync"
)

var db *sql.DB
var mutex sync.RWMutex

func GetDb() *sql.DB {

    mutex.Lock()
    defer mutex.Unlock()

    err := db.Ping()
    if err != nil {
        db, err = sql.Open("mysql","dsn...")
        if err != nil {
            panic(err)
        }
    }

    return db
}

func main() {

    var err error
    db, err = sql.Open("mysql","dsn....")
    if err != nil {
        panic(err)
    }

    http.HandleFunc("/",func(w http.ResponseWriter, r *http.Request) {

        row := GetDb().QueryRow("select...")
        // scan row

        fmt.Fprintf(w,"text from database")
    })

    http.ListenAndServe(":8080",nil)
}

Which of these ways are the best or is there another way which is better. Is it a bad idea to have multiple request use the same database connection?

It's unlikly I will create an app that runs into mysql connection limit, but I don't want to ignore the fact that there's a limit.

The best way is to create the database once at app start-up, and use this handle afterwards. Additionnaly, the sql.DB type is safe for concurrent use, so you don't even need mutexes to lock their use. And to finish, depending on your driver, the database handle will automatically reconnect, so you don't need to do that yourself.

var db *sql.DB
var Database *Database

func init(){
  hostName := os.Getenv("DB_HOST")
  port := os.Getenv("DB_PORT")
  username := os.Getenv("DB_USER")
  password := os.Getenv("DB_PASS")
  database := os.Getenv("DB_NAME")
  var err error
  db, err = sql.Open("mysql", fmt.Sprintf("%s:%s@tcp(%s:%d)/%s", username, password, hostName, port, database))
  defer db.Close()
  if err != nil {
     panic(err)
  }
  
  err = db.Ping()
  if err != nil {
    panic(err)
  }
  
  Database := &Database{conn: db}
   
} 

type Database struct {
  conn *sql.DB
}

func (d *Database) GetConn() *sql.DB {
   return d.conn
}

func main() {
    row := Database.GetConn().QueryRow("select * from")
}

I'd recommend make the connection to your database on init().
Why? cause init() is guaranteed to run before main() and you definitely want to make sure you have your db conf set up right before the real work begins.

var db *sql.DB

func GetDb() (*sql.DB, error) {
   db, err = sql.Open("mysql","dsn...")
   if err != nil {
      return nil, err
   }
   return db, nil
}

func init() {
   db, err := GetDb()
   if err != nil {
      panic(err)
   }
   err = db.Ping()
   if err != nil {
      panic(err)
   }
}

I did not test the code above but it should technically look like this.