Nice video and great to see some example go code. All I would say is it looks like your going to create four "GET" endpoints for each of the CRUD operations. In true Web API you would centre the CRUD operations around a single URL for each entity using the appropriate HTTP verb for each operation - GET, POST, PUT and DELETE.
Yep! Typical web APIs use an HTTP verb that matches the action that one wants to perform. In this case I made a decision to do things a bit differently, and I will explain why in my next video. Thanks!
Yes, for very simple code, it is easy and productive just write the code without frameworks, and that is very relevant now with the hype of micro-services arch.
Very nice
Nice video and great to see some example go code. All I would say is it looks like your going to create four "GET" endpoints for each of the CRUD operations. In true Web API you would centre the CRUD operations around a single URL for each entity using the appropriate HTTP verb for each operation - GET, POST, PUT and DELETE.
Yep! Typical web APIs use an HTTP verb that matches the action that one wants to perform. In this case I made a decision to do things a bit differently, and I will explain why in my next video. Thanks!
Yes, for very simple code, it is easy and productive just write the code without frameworks, and that is very relevant now with the hype of micro-services arch.
The video and content are great, but the loud keyboard is distracting