GORM VS SQLBoiler

Do you like an ORM like eloquent for Laravel? Then I can recommend GORM https://gorm.io/

Good ORM library: https://gorm.io/

GORM

Well, if you look at Gorm's prepare_stmt.go you see that it is a thin wrapper around a database/sql.Stmt. And if you look at database/sql.Stmt you see that it's a sort of handle to an abstract entity that it creates in the database.

Writer service consumes kafka topics, process messages writing to postgres and publishes successfully processed messages to kafka. For working with postgres in Go in my opinion the best choose is pgx, but if you need query builder very good library is squirrel, personally don't like orm's, but usually as have seen, teams often uses gorm, it's up to you. ProcessMessages method listening kafka topics and call specific method depends on topic:

gorm's performance I believe is fairly impressive at this point. While it was bad at first, they put a lot of effort in the v2 release to make it great. Check out: https://github.com/go-gorm/gorm/issues/3055

Sure. You can do this, but I would honestly recommend to only do this in test code, if at all. Otherwise, you should aim to keep types and by that the according API to interact with your DB schema static and consistent. An easy way to do this would be to use an object relational mapper (ORM) library like gorm.

Once in sqlite you can use something like https://gorm.io/ (or use a golang sqlite package like: github.com/mattn/go-sqlite3) to work with the data.

If you and your team currently don't have any specific requirements, I'd advice to choose an abstraction library that have supports for most common dbs (eg. gorm or bun) and start with whatever db you are more used to.

DB abstractions: - gorm - go-pg - bun - sqlx

It seems you forgot sqlboiler [1] which is something like "write SQL schema, parse SQL schema, generate Go structs and functions to query the schema". Not quite like generating activerecords, I think.

[1]: https://github.com/volatiletech/sqlboiler

I was expecting the article to contain a note about SQLBoiler (https://github.com/volatiletech/sqlboiler) and why they didn't use it, but there is no. So I was expecting SQLBoiler to be heavily mentioned in the comments, but it's not the case.

I you want to see a (slightly heated) debate about `sqlc` versus SQLBoiler with their respective creators: https://www.reddit.com/r/golang/comments/e9bvrt/sqlc_compile...

Note that SQLBoiler does not seem to be compatible with `pgx`.

You might want to have a look into SQLBoiler. https://github.com/volatiletech/sqlboiler

Consider SQL Boiler because it can integrate directly with an existing database.

Depending on your preferences, sqlboiler uses the DB as source of truth for generating structs and has nice querying features

DB Management: https://github.com/volatiletech/sqlboiler -- this follows a data first model, aka your database schema will create go code, not the django way where Py code updates the DB. https://github.com/amacneil/dbmate -- I use it to manage my DB schema.

volatiletech/sqlboiler is another ORM available for Go, it's database-first instead of code-first like gorm, what this means in practice is that sqlboiler generates type-safe Go code to act as an ORM, to date it supports postgres, mysql, sqlserver, sqlite and cockroach db.

If you complain about Golang's ORM, the best way is to generate code based on Database Schema, Go doesn't have meta programming as in Ruby or bytecode generation as in Java. You can use library like sqlboiler or generate your own.

https://github.com/volatiletech/sqlboiler is my personal favorite