ent VS Goyave

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

Take a look at Goyave, it is inspired by Laravel on some aspects. It's focused on REST APIs only. I wouldn't say it's "the best" because there is no best, it always depends on your needs. Anyway, yesterday I released the first preview version of the v5, a rewrite of the framework trying to solve many weak points of the previous version. It's poorly documented for now because it is still WIP and I wouldn't recommend building production applications with it. Stick to v4 for this for now.

I can't say it rivals because it's still far from that, but I'm working on Goyave. The goal is to make a complete package so you can focus on your business logic as much as possible. It's focused on REST APIs only.

You can try https://goyave.dev/ ?

Take a look at Goyave.

Check out Goyave and see if it would fit your needs.

Goyave is not widespread but it's inspired by Laravel on some aspects. Try it out!

Hey! That's the goal of Goyave, a framework I'm working on. Its creating was motivated by the same complaint you have.

I'm using Goyave, removes the hassle of setting up a lot of things yourself for bigger projects or APIs that are going to be exposed to the internet. Otherwise for internal services it's probably overkill.

Take a look at Goyave.