client_golang VS chi

Prometheus, an open-source systems monitoring and alerting toolkit, has client libraries that allow you to instrument your services in a variety of languages. Here's an example of how you might use the Go client library to expose metrics on an HTTP endpoint. We will leverage the prometheus go client to expose metrics and create them.

Monitoring prometheus, grafana

I'd recommend github.com/victoriametrics/metrics for exporting custom metrics in Prometheus format. It is easier to use than the github.com/prometheus/client_golang.

Start at the official documentation and the Go client library .

DataDog can read Prometheus metrics. Note that this approach works for metrics but not for traces although you can configure DataDog to receive OpenTelemetry traces as well https://github.com/prometheus/client_golang

For Go, the standard is to use Prometheus and the Prometheus Go client library.

I use go-chi for handling routes and to server static file(stylesheet).

This will be the structure of our project, we will use PostgreSQL as the database, go chi to create our endpoints, go dot env to import our environment variables.

go-chi: is a lightweight, idiomatic and composable router for building Go HTTP services.

Go Chi para criar nossas rotas

For HTTP I'd look at Chi https://github.com/go-chi/chi

In fact, it has zero dependencies outside of std lib in it's core: https://github.com/go-chi/chi/blob/master/go.mod

Interesting. go-chi added it as a middleware 4 months ago, but its not in the module docs since they haven't tagged a version since Dec 2022: https://github.com/go-chi/chi/blob/master/middleware/request_size.go