GORM VS ent

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

For anyone interested, it looks like there's an open-source version (close, at least) to Ent at https://github.com/ent/ent.

I have not used Ent (https://entgo.io/) yet since I am typically anti-ORM but Ent solves things in ways that make me think I could tolerate it. The team has had really good velocity for adding things to it so I at least want to do a proof of concept with it in the future.

I’ve been really happy watching the progress of the https://entgo.io/ project and expect it to gain adoption and popularity.

While working on Ariga's graph query engine, we saw the opportunity to greatly improve the performance of many use cases by building a caching layer. As heavy users of the Ent Framework, it was only natural for us to implement this layer as an extension to Ent. In this post, I briefly explain what caches are, how they fit into software architectures, and present entcache - a cache driver for Ent.

ent with gqlgen.

If you're interested in databases and APIs (e.g. GraphQL and OpenAPI), you're welcome to Ent (github.com/ent/ent). We have a great and friendly community, and you can feel free to ping me on our Slack channel privately if you need some support or guidance. Good luck!

In a previous blogpost, we presented to you elk - an extension to Ent enabling you to generate a fully-working Go CRUD HTTP API from your schema. In the today's post u/MasseElch introduces to you a shiny new feature that recently made it into elk: a fully compliant OpenAPI Specification (OAS) generator.

A few months ago, u/_a8m_made a silent but highly impactful contribution to Ent's core, the Extension API. While Ent has had extension capabilities (such as Code-gen Hooks, External Templates, and Annotations) for a long time, there wasn't a convenient way to bundle together all of these moving parts into a coherent, self-contained component. The Extension API which we discuss in the post does exactly that.

for reference fb does use a graph database that mimics graph properties (https://github.com/ent/ent)