go-doudou VS sqlx

Github repo: https://github.com/unionj-cloud/go-doudou Latest release: v1.3.2

Update documentation to latest version https://go-doudou.github.io

If you like sqlx, I recommend you to have a look at go-doudou built-in lightweight orm based on sqlx. It can do struct to table and table to struct migration/sync, generate dao layer code to simplify your single table CRUD operations, and it also can print SQL query with parameters substituded along with opentracing compatible trace ID for locating problems, and it will have more features coming such as cache layer... Here is the repo: https://github.com/unionj-cloud/go-doudou

I recommend go-doudou for you: https://github.com/unionj-cloud/go-doudou Here is online documentation: https://go-doudou.github.io/

Please take a look at https://github.com/unionj-cloud/go-doudou This is a microservice framework written in Go. I opened it a year ago. It's production ready, but there are a lot of featues not implemented yet. I hope community can help me build it together.

Go-doudou released v1.0.3: https://github.com/unionj-cloud/go-doudou/releases/tag/v1.0.3 Add full support for Alibaba Nacos configuration management and Ctrip Apollo configuration management Documentation: https://go-doudou.github.io/guide/configuration.html

Hi gophers, go-doudou released v1.0.0 version today: https://github.com/unionj-cloud/go-doudou/releases/tag/v1.0.0. And I finished online documentation for go-doudou though there is only English version: https://go-doudou.github.io. I also uploaded a real-world word cloud application to github: https://github.com/unionj-cloud/go-doudou-tutorials/tree/master/wordcloud. You can use this project as scaffold to build your microservices.

In this tutorial, I will introduce go-doudou microservice framework to you. Go-doudou has built-in service register, discover and fault tolerance features based on gossip protocol, and it uses gorilla/mux as http router, and uses golang interface as IDL(Interface Definition Language). Go-doudou is an IDL compiler and server/client code generator tool at first, then it becomes a microservice framework. Its RESTful version is stable and production ready, while grpc version is in early development.

We've always used https://github.com/jmoiron/sqlx which is just the standard package + mapping to/from structs.

You can use this https://github.com/jmoiron/sqlx

I will be using sqlx to execute queries and map columns to struct fields and vice versa, sqlx is a library which provides a set of extensions on go's standard database/sql library.

sqlx + squirrel ftw

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.

IDE: use whatever make you productive. I personally use vscode. VCS: git, as golang communities use github heavily as base for many libraries. AFAIK Linter: use staticcheck for linting as it looks like mostly used linting tool in go, supported by many also. In Vscode it will be recommended once you install go plugin. Libraries/Framework: actually the standard libraries already included many things you need, decent enough for your day-to-day development cycles(e.g. `net/http`). But here are things for extra: - Struct fields validator: validator - Http server lib: chi router , httprouter , fasthttp (for non standard http implementations, but fast) - Web Framework: echo , gin , fiber , beego , etc - Http client lib: most already covered by stdlib(net/http), so you rarely need extra lib for this, but if you really need some are: resty - CLI: cobra - Config: godotenv , viper - DB Drivers: sqlx , postgre , sqlite , mysql - nosql: redis , mongodb , elasticsearch - ORM: gorm , entgo , sqlc(codegen) - JS Transpiler: gopherjs - GUI: fyne - grpc: grpc - logging: zerolog - test: testify , gomock , dockertest - and many others you can find here

This is the same situation I saw 20 years ago. Back then, all the managers were pushing development in Oracle tools. Those managers grew up on Oracle and Java was too modern for them. Now the situation is similar. Managers used to do things in Java and now they are still pushing Java. In fact, today Java brings nothing but problems. When I see a new project starting on Java it is always some big desperation. For a comparison of Java and Go, just look at the documentation for SQL. For go: https://pkg.go.dev/database/sql (31 pages) and maybe https://jmoiron.github.io/sqlx/ (12 pages). In Java only one class is 59 pages (https://docs.oracle.com/javase/8/docs/api/java/sql/ResultSet.html) and look how many of those documents there are: https://docs.oracle.com/en/java/javase/13/docs/api/java.sql/java/sql/package-summary.html and on top of that we have javax.sql - https://docs.oracle.com/javase/8/docs/api/javax/sql/package-summary.html And even then you use Hibernate for example, where the documentation has 11 manuals and of those the User Guide has 353 pages - https://docs.jboss.org/hibernate/orm/6.2/userguide/html\_single/Hibernate\_User\_Guide.html

sqlx