Hi,
In my case, I choose building APIs with Go when I start to notice things are getting messy in Wappler. Because Go is a typed programming language, it’s easy to define data structures (e.g.: of a JSON) and perform operations in it. I don’t have to worry about Wappler’s UI not following my less-usual structures and I use Visual Studio Code’s Intellisense (with the Go extension) to get auto-complete.
These tools are useful to convert JSON to Go structures:
https://mholt.github.io/json-to-go/
https://json2struct.mervine.net/
Regarding frameworks, lately I’ve been using this one because it’s similar to NodeJS’ Express:
That framework uses a non-standard HTTP server, it might be faster than Go’s native net/http server but it might also complicate debugging when your code breaks. At the moment I’m ok with such risk.
Other framework alternatives that are generally well-known and use the standard net/http server are:
This one’s “idiomatic”, meaning it aims to follow Go’s official net/http design pattern:
Something to be aware is the Go community is not very fond of frameworks, unlike other programming languages, so ideally you’d stick to a framework that’s “idiomatic” (chi), but in the end it’s a balance between “idiomatic” and “productive” you have to choose, so that’s why I’ve been using Fiber for my latest projects