We’ve got the main service going. It can take requests and process them. Some requests, depends on how you design it, may take a long time to process. Normally for long running tasks like those, we put them behind the scene and have someone working on it. …

Something I noticed: Important projects always go to certain individuals. These individuals are smart but not necessarily much smarter or better programmers than the rest of us, so why? I took a closer look at their work patterns and found something: they don’t always only work on high profile projects…

Let’s put everything we’ve got together. We create a main.go which calls… func main() { r := gin.Default() db, error := tools.SetupDB() // assuming we get a function to do this and returns a *gorm.DB instance routes.SetupRoutes(r, db) // calls route.go file to set up…

We’ve got our controller. Now it’s just a matter of fact that we need to connect it to some route. Remember we have a UserController struct and NewUserController method to create this struct. Since we have defined the routes already as such func NewUserController(r *gin.Engine, userManager *managers.UserManager) { userController…

We are reaching our controller level. The goal is to create a controller that can get the request from routing and process it with our manager. We want to first define our controller struct… type UserController struct { } Since we are really to access the manager, we can use…

Now that we have our repos and their interfaces up and ready, we can start connecting to the managers or services. I will use these 2 terms interchangeably in this article. Going back to our repo logics // ... all the same code above CreateUser from the previous section func (repo…

Last time we’ve created a model that we can use to marshal and unmarshal for JSON. It also acts as the object part of ORM for GORM. type User struct { UUID string `gorm:"primaryKey"` Name…

I’ve been checking out the packages for SQL. There are sqlc, sqlx, and GORM that are publicly available. There’s a more detailed blog about the comparison. The short version is, sqlx is more performant, but GORM provides ORM structure which I think is cleaner, so I went with GORM. Since…

Go has its own http package. Normally a request can be handled by using net/http package and simply do http.HandleFunc("/ping", func(w http.ResponseWriter, r *http.Request) { // do what we wanna do with the request here }) _ = http.ListenAndServe(":8080", nil) the ListenAndServe given :8080 indicates the service will be listening…