goa
ent
Our great sponsors
goa | ent | |
---|---|---|
40 | 145 | |
5,453 | 14,838 | |
0.7% | 1.3% | |
9.3 | 8.3 | |
5 days ago | 8 days ago | |
Go | Go | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
goa
-
Microservices communication
See https://goa.design/. It automates all the comms stuff, so you just write: 1) a design file showing your functions, 2) an implantation of those functions, and 3) a very generic "main.go" (basically the same for all your services) that decides "how is this exposed over gRPC or REST or other comms?". The rest of the code is generated.
-
Create Production-Ready SDKs with Goa
Perhaps the easiest way to find out how to do something (especially when using Meta) is to search the test cases when you have cloned the source code.
-
Which is the best framework to create web apps with go?
If you really need a framework, you can take a look at Echo or, for a contract-first approach, https://goa.design/
-
OpenAPI v4 Proposal
Few folks in here are (rightly) frustrated with the code generation story and broader tooling support around the OpenAPI standard. I've found a few alternative approaches quite nice to work with:
- Use a DSL to describe your service and have it spit out the OpenAPI spec as well as server stubs. In other words, I wouldn't bother writing OpenAPI directly - it's an artifact that is generated at build time. As a Go user, I quite like Goa (https://goa.design/) but there are others shared in here like TypeSpec.
- There are situations where sticking a backend-for-frontend (BFF) in front of APIs can yield great productivity boosts. For example, in the past we built a thin GraphQL proxy that calls out to a poorly structured REST API. Integrating with that was much more convenient. Most recently, I've been playing with a BFF built with tRPC (https://trpc.io/) which calls out to a REST API. It seemed to provide an even better experience if you use TypeScript on the front-end and in the BFF. It does not have a codegen step and I was really pleased with how fast I could iterate with it - granted it was a toy project.
-
Beginner-friendly API made with Go following hexagonal architecture.
One of the biggest issues I see is that you are using the same models for API as you are for the database. That wouldn’t fly in a real work system. And even though your doing simple CRUD I would introduce another layer for business logic. You should never have the Controller calling you database code directly. It never “stays” that simplistic. One of the easiest ways to deal with this is to use Goa. https://goa.design/ It takes care of generating your API models and it creates the Interfaces to implement for your business logic. Furthermore it creates OpenAPI documentation (something missing in this design that is a must for commercial development).
-
Go with PHP
I left PHP for Go.
- with http://sqlc.dev I don't have to write ORM or model code anymore.
- with http://goa.design I can have well-documented API's that any team can generate a client for in any language. It also generates the HTTP JSON and gRPC servers for me so I can focus on my logic.
- with https://github.com/99designs/gqlgen I can define GraphQL revolvers that play well with sqlc (any RDBMS) or I can use a key-value store.
- speaking of key-value stores, Go allows them to be embedded! Even SQLite now has the https://litestream.io/ project to make it super simple to use a durable, always backed-up SQLite database even in a serverless context.
Go is faster, uses less memory, and has really-well designed stdlib without all the bugs I used to face trying to use the PHP stdlib.
-
Do you really need microservices?
Goa and Kong are some of the best frameworks to develop and deploy microservices. They provide features such as out-of-the-box support for service discovery, routing and authentication that make it easier to build more complex applications. There are also newer architectural frameworks with less steep learning curves like GPTDeploy that lets you build and deploy microservices with a single command.
-
Dumb question about APIs, Mux and Go
Or the one we use at work: https://goa.design/ Goa does a lot more and maybe more than you need. We use it as it can generate both REST and gRPC as well as API models and OpenAPI documentation (JSON and YAML).
- Why is gin so popular?
-
Does this project structure make sense?
I typically use Goa for my controller. It makes the API Controller, API models, and OpenAPI Documentation. Making the OpenAPI documentation can be a pain, so this really helps. https://goa.design/
ent
-
Concurrency Control in Go with Ent ORM and MySQL
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.
-
Go ORMs Compared
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.
-
Stop using entgo...please
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.
- Pocketbase: Open-source back end in 1 file
-
Why Golang instead of Rust to develop the Krater desktop app
The ent orm for golang actually does some useful work for you. https://github.com/ent/ent
- Open-sourcing SQX, a way to build flexible database models in Go
-
Learning Go for Backend/Fullstack development?
Backend Database interaction with entgo
- Ent ORM for Golang
- My Issue With ORMs
-
What project architecture/structure would you recommend?
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
What are some alternatives?
Gin - Gin is a HTTP web framework written in Go (Golang). It features a Martini-like API with much better performance -- up to 40 times faster. If you need smashing performance, get yourself some Gin.
GORM - The fantastic ORM library for Golang, aims to be developer friendly
go-kit - A standard library for microservices.
SQLBoiler - Generate a Go ORM tailored to your database schema.
GoSwagger - Swagger 2.0 implementation for go
sqlc - Generate type-safe code from SQL
oapi-codegen - Generate Go client and server boilerplate from OpenAPI 3 specifications
sqlx - general purpose extensions to golang's database/sql
Echo - High performance, minimalist Go web framework
Xorm
gqlgen - go generate based graphql server library
go-pg - Golang ORM with focus on PostgreSQL features and performance