Our great sponsors
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
From my experience most of the stuff you can do with go, you can do with java and vice versa. I have written networking applications based on netty.io and written webapps with go. I would say its other factors that play a big role.
This is very frequent question from ppl coming from Java and similar languages. It might sound strange, but you will see it's absolutely valid: no frameworks. Just forget this word =) In Go you will most of the time use standard library, and some helper libraries from 3rd party toolkits. For instance in case of some "average" REST microservice I would imagine `http.Server` from standard library and `mux.Router` from `github.com/gorilla/mux` (take a look at other repos within gorilla). For DB access it could be `database/sql`, maybe `github.com/jmoiron/sqlx` or maybe `
gorm.io/gorm`, or `github.com/go-pg/pg` if you need something more feature-rich. I would avoid using `go-kit` and `go-micro` "frameworks" unless you have some special requirement for it. But you can take a look to have an idea of what Go "framework" may look like.