go-pg VS ent

I usually work with PostgreSQL and have used https://github.com/go-pg/pg. https://github.com/uptrace/bun is its successor.

bun and go-pg both seem to work fairly well for these kind of purposes.

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.

I think you are looking for ent https://github.com/ent/ent which has nice graphql integration.

Check out https://entgo.io/ I like the approach to define an entity schema first and let handle entgo the query part.

ent has the nicest integration with graphql (using gqlgen) that I’ve seen with Go, generating almost all the code needed for resolvers and some graphql commons like Node interface and Connection pattern. It also supports PostgreSQL out of the box.

With Atlas, the migration directory can function as the desired state. Thus, you can use Atlas without changing your existing codebase. We use this approach in Ent and it works great for many users. Atlas also supports auth-generating migrations for other migration tools, like Flyway, Liquidbase and various others.

Ent is a framework we created at Facebook and open-sourced a few years ago, and it has grown a lot since then. You're welcome to give the doc a quick read. Still, a summary is it uses a "schema as code" approach based on code generation with plenty of cool features built-in, such as seamless GraphQL/gRPC/OpenAPI integration, hooks, privacy (authorization support), a templating infra that makes it extensible and much more.

Ent is the migration that uses Atlas as a migration engine. The Ariga team maintains both projects.

This is approximately what Ent does.

Try https://github.com/ent/ent :D

I can recommend https://entgo.io/ , ORM with graph semantics + GraphQL/REST/GRPC API generator