Extending the REST branch to show off a CRUD implementation

[joms]

Hi!

I love your article series on the ultimate Golang project structure, and it gives a good overview on how to implement a nice structure for building api services in Golang. However, I feel like the blueprint repo lacks something to make the articles more useful, and showing off how the structure could help one create more powerful services.

An example is Services where you say one could do more filtering, but all you show is calling the Get method of the UserDAO, which makes it feel like it's not really useful. What I think would really help showing off how powerful this structure could be, is creating a full Create, Read, Update, Delete for a user api, utilising all the functionality you describe in the article.