ent VS grimoire

In this article, we'll delve into the world of concurrency control in Go, specifically focusing on the optimistic locking approach. We'll explore its implementation using Ent ORM to illustrate how to manage data consistency when multiple users interact with the same resource. Keep in mind that this example serves as a simplified illustration, and real-world booking systems involve a many of additional complexities. However, the core concepts presented here provide a solid foundation for understanding optimistic locking in Go applications. Feel free to explore the complete source code in my GitHub repository for a more in-depth look at the implementation.

ent is a fairly recent ORM that uses a code-first approach where you define your schema in Go code. Ent is popular thanks to its ability to handle complex data models and relationships elegantly. It's statically typed, which can help catch errors at compile time. However, the learning curve might be steeper compared to more straightforward ORMs like GORM. It's a good fit for applications where complex data models and type safety are priorities.

If you found this article, than you are probably similar to how I was a few months ago. I started a project in Go that required a SQL backend and I wanted to use any tool that would help me build this backend quickly. I stumbled upon entgo (an ORM for Go) and decided to give it a try.

The ent orm for golang actually does some useful work for you. https://github.com/ent/ent

Backend Database interaction with entgo

You can use entgo.io for ORM stuff, it also has entgql extension that integrated with GQLGen. See more at the document: https://entgo.io/docs/tutorial-todo-gql

A long time ago (9 days), on a distant land (/r/selfhosted), the project Grimoire was announced. Its promise was simple: make bookmarking magical and fun! And open-source, of course!

Hello there! I'm Robert, the creator of Grimoire.

I'm very flattered by such good observations and the warm welcome for this project. I won't be able to respond to every comment from you guys, but you bet I will read them all and take notes!

For now, Grimoire is at 1/10 of its potential, and I will work hard to make it worthy of being a good contender for your default bookmark manager. Definitely, it's missing many features, like a dedicated browser extension, import/export capabilities, and better documentation, and I'm well aware of that.

Was the launch rushed? Maybe, but I thought it would be great to hear your opinions and perhaps even appeal to some potential contributors (wink wink).

For now, I want to address the most common issues that prevent some of you from even running and testing it (clearly an oversight on my side). Then I will write a blog post on https://grimoire.pro to answer some of your questions and doubts, so (if not now, but maybe in the not-too-distant future), give it a chance.

Thank you again, and big kudos to user hunderbong for mentioning Grimoire on HN!