Endless API creation

Hi everybody, I just wanted to share my side. Since I started using Go on my first job I liked it very much for how structured it is, how straight forward with the coding style. Now, I have been trying to build my portfolio in golang and the only idea I have with Go is API. (Some repos are unfinished, this is by far I am working on, also unfinish)

Sharing my repo:

https://github.com/XaiPhyr/rdev-go-api

How did you guys move on from creating API? What projects are you most fond of? Thank you very much in advance

PS: the reason I’m doing this is I want to apply for a job in Golang and wanted to focus my Golang skills

Review which Go features you haven’t used or have used little and create projects with them. As you mentioned in your note, you created a web API, so I think a logical next step would be to add HTML processing, upload files and process them with Go, and populate databases with the information from those files. Another step could be microservices and cloud computing. You should also strengthen your knowledge of goroutines and channels….

Just my two cents…

Go is very powerful you can do TUIs, data processing (structs are great for this). I tend mostly use it as a backend but the way you have to use it as a networking type tool or systems related is very different.

Go routines make more sense in these non api type of projects as well. I would say if you try to do something that involves mutex (e.g. locking a file for editing) and try to display outputs live it can push you. Especially on the memory side too. Maybe even some sort of pipeline style thing.

In my personal projects my main use is still mostly apis tbf.