Excellent video Stuart. I tend to prefer versioning at the endpoint level. I agree with you about versioning only at the major number. I never understood the need of doing it as a minor. I can't come up with a good scenario for it. By the way, the style of this video was extremely professional and easy to follow.
Thanks mate! Honestly, I think it's there for people that like semantic versioning and think that you have your API surface at the same version as your code, which is wrong - they should be decoupled!
Can you make a video about using identity server as a centralized authentication provider like google, auth0 etc. with multiple clients (blazor wasm, ..)
Want to know how to test AWS locally like a pro, checkout this video on Xunit & Localstack: th-cam.com/video/Ad7wruPBp3M/w-d-xo.html
Excellent video Stuart. I tend to prefer versioning at the endpoint level. I agree with you about versioning only at the major number. I never understood the need of doing it as a minor. I can't come up with a good scenario for it.
By the way, the style of this video was extremely professional and easy to follow.
Thanks mate! Honestly, I think it's there for people that like semantic versioning and think that you have your API surface at the same version as your code, which is wrong - they should be decoupled!
Can you make a video about using identity server as a centralized authentication provider like google, auth0 etc. with multiple clients (blazor wasm, ..)
I've added this to the list of ideas, thanks for the suggestion!
Increase font size
Versioning should be done in API Gateway
Potentially... lots of factors to consider and there's never 1 size fits all :)