Goyave VS GORM

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.

GORM is a comprehensive ORM tool in Go, offering a code-first approach which allows defining database schemas using struct tags in Go. It's known for its developer-friendly nature, making it suitable for both beginners and experienced users. GORM supports a variety of SQL databases like MySQL, PostgreSQL, and SQLite. It's designed to be flexible, allowing developers to drop down to raw SQL when necessary. However, it's important to be cautious about its performance implications in large-scale applications.

Homepage: https://gorm.io/

Since most of these APIs will be simple CRUD (Create/Read/Update/Delete) endpoints, let's build this service using GORM, an ORM library that makes building CRUD endpoints really simple.

After successfully configuring the application, it's time to delve into integrating the data layer. For this purpose, I will utilize gorm, a powerful SQL ORM that facilitates rapid development of the data layer using model structs.

For basic INSERT ... VALUES ... or SELECT ... WHERE ... JOIN ..., use a library such as GORM. For INSERT .... SELECT ... statements where one combines two round trips (SELECT and INSERT) into one, ORMs have a hard time performing this query. Particularly when you start doing joins. Joins are the heart of Relational database theory (they denote relationships). So get to know what an INNER, LEFT, RIGHT and OUTER join is and why you would use them. Also learn INSERT ... SELECT ...

I have never hated gorm and it serves me well. However I tend to feed it raw SQL very often.

Array of values with embedded value all pointed to the last value, reflect code was broken: https://github.com/go-gorm/gorm/pull/5901 data corruption