todo-api-microservice-example
Squirrel
todo-api-microservice-example | Squirrel | |
---|---|---|
17 | 52 | |
979 | 6,540 | |
- | 1.1% | |
8.6 | 2.4 | |
8 days ago | 13 days ago | |
Go | Go | |
MIT License | GNU General Public License v3.0 or later |
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.
todo-api-microservice-example
-
While Learning Haskell Developing Project
Hello guys im a self teach coder. im working with golang atm because this great project speed up my learning curve: https://github.com/MarioCarrion/todo-api-microservice-example
-
Open source projects to look at for best practices?
With that being said, if you're looking for something friendlier, I share my own educational repo, still a WIP but it should help you with the basics.
-
Is there a standard file in Golang from which packages could be installed? Yes, I am aware about go.mod, but hear me out.
internal/tools and
-
Hexagonal architecture and mocking
You are going to need to add a domain package where the Beer type and all the logic associated to that type is defined to avoid the cyclical dependency. I typically follow this approach by using internal as the domain package that then other packages like services, data stores or transport use.
- Working with microservices in a monorepo
-
DDD file structure & cyclic dependencies
Here's my approach; a few worth-mentioning packages in there: * service defines the use cases, it's a glue between the domain model and repositories. * rest defines the http handlers uses the service types via dependency injection (see main.go) * postgresql concrete repository example (there are other implementations for other data stores like kafka, redis, etcetera.
-
Example of a well written and structured RESTful API or web service?
Other redditors mentioned some good resources, I'm going to shamelessly plug mine as well; either way after you are done with whatever tutorial you use I recommend you to look at the Exposure Notifications Server, reading the source code should help you learn other best practices.
-
Golang for backend
One word of advise I can give you is that building a production-grade microservice in Go takes a bit; not because of the language but because you have consider the tradeoffs when choosing different packages to connect everything to make it work (because there's no Django, Ruby on Rails or Spring), I have an educational repository (still work in progress) trying to describe what I've learned from the last 5 years after successfully deploying multiple services to production where multiple engineers contribute and collaborate together; perhaps that could help you.
-
How to avoid "import cycle not allowed" when defining related models in different packages?
With all of that being said I have an educational repository demonstrating this structure, I've been using it in real life for about 5 years already and I've successfully delivered services to production multiple times where multiple engineers contribute and collaborate together.
-
Good example of production grade rest api without an ORM
You may want to checkout the "Exposure Notifications Server" project; I also have a similar (educational) project that uses the Repository Pattern.
Squirrel
-
Building RESTful API with Hexagonal Architecture in Go
It uses Gin as the HTTP framework and PostgreSQL as the database with pgx as the driver and Squirrel as the query builder. It also utilizes Redis as the caching layer with go-redis as the client.
-
Working with postgres in GO.
I would add Squirrel to PGX https://github.com/Masterminds/squirrel
-
how to avoid writing dreadful SQL statements
I have written about this before, and my thoughts always settle on using a query builder. I've built a simple one, which works for what I need, but there are more feature complete ones out there such as squirrel. I've also written about how you can implement a simple CRUD library for database interactions using generics and query building to have that nice middle-ground between an ORM and query building.
-
How do I enable filters for the user without writing redundant SQL?
Now for the dynamic queries you have to be really careful to prevent SQL injections, there are bunch of different ways to do it but I typically recommend using a package such as squirrel that lets you do this easily, you use it to generate the plain SQL you need (and then use sqlx, database/sql, pgx or whatever you prefer) or use it directly querying the database directly.
-
Best sqlc alternative for dynamic queries?
Here are 2 options for you * https://github.com/huandu/go-sqlbuilder * https://github.com/Masterminds/squirrel
-
Golang RESTAPI boilerplate repository
https://www.reddit.com/r/golang/comments/vq98ud/what_sql_library_are_you_using/ Jet havn't used but is one that looks promising! Otherwise I'm one of the purests, db/sql and https://github.com/Masterminds/squirrel
-
Why is Raw SQL preferred over ORM in go?
I think he means an sql builder like squirrel. This allows dynamic queries, but more important you can reuse function that build a where clause so you can get a count and query with that.
-
Does Go, has something similar to Laravel eloquent (ORM) ?
I'd rather suggest the use of tools more aligned with the core concepts of the language such as sqlx, which is an extension of the database/sql standard library. It allows you to use models/structs to map your tables but you have more control over the SQL statements you use to perform queries and the like. You can combine sqlx with Squirrel to build queries from composable parts.
-
Are there any decent ORMs in Golang?
But using a query builder, something like squirrel or (plug) bqb, allows you to actually write SQL (or something close to it) when you need it but also handles the nasty string building bits. Though I agree that ORMs are not always bad, especially for small projects with well-defined scope.
-
GORM
Plug for bqb as a query builder, but there's also squirrel which works pretty well too.
What are some alternatives?
fx - A dependency injection based application framework for Go.
goqu - SQL builder and query library for golang
svc-fizzbuzz - A simple fizzbuzz microservice
sqlx - general purpose extensions to golang's database/sql
franz-go - franz-go contains a feature complete, pure Go library for interacting with Kafka from 0.8.0 through 3.6+. Producing, consuming, transacting, administrating, etc.
GORM - The fantastic ORM library for Golang, aims to be developer friendly
waypoint - A tool to build, deploy, and release any application on any platform.
InfluxDB - Scalable datastore for metrics, events, and real-time analytics
exposure-notifications-server - Exposure Notification Reference Server | Covid-19 Exposure Notifications
sqlc - Generate type-safe code from SQL
explicit-architecture-php - This repository is a demo of Explicit Architecture, using the Symfony Demo Application.
sqlx - 🧰 The Rust SQL Toolkit. An async, pure Rust SQL crate featuring compile-time checked queries without a DSL. Supports PostgreSQL, MySQL, and SQLite.