ASP.NET Core 8 Web API in Clean architecture from scratch

No video

ASP.NET Core 8 Web API in Clean architecture from scratch

Рет қаралды 19,011

Fullstack Dev

Күн бұрын

Пікірлер: 18

@AzureFullstackDev 6 ай бұрын

Full course: fullstackdeveloper.tech/c/web-api-ca

@bmassioui Ай бұрын

I really like the covered points for this video, specifically the Authentication-Authorization concerns, for this purpose I bought the course directly, thanks.

@AzureFullstackDev Ай бұрын

Thanks, glad you liked it Enjoy the rest of the course

@efragafd 2 ай бұрын

Good video. And a good trick to engage us to buy the Udemy course, but actually I did buy it and from my perspective, the course is TOTALLY RECOMMENDED. It goes deeper into Clean Architecture patterns and explains the concepts very well. I hope more content related here and in Udemy. Congrats!

@AzureFullstackDev 2 ай бұрын

thanks for the feedback, Im glad you liked it :) Im currently fishing up a MS SQL course (but in Polish), but after that I do have a plenty of content to record in English as well, both youtube and udemy courses (such as :entity framework, ASP.NET MVC, Azure services, etc.)

@mattl7599 2 ай бұрын

@@AzureFullstackDev I would love to see a topic on extending a rest API with clean architecture to support multi tenants.

@rorycawley 4 ай бұрын

The example you give 9:51 show GET request with a request body. A request body with GET doesn't often work since some libraries don't expect a body with GET.

@christian.mar.garcia 3 ай бұрын

Also, I have seen that some firewalls block the request body for GET operations. The POST is for sending body data.

@AzureFullstackDev 3 ай бұрын

true, it depends on the library, but it's not explicitly prohibited by the HTTP standard. It's a rare case to use such HTTP request, but since GET URLs have a maximum length limit, which varies across different browsers and servers. Including large amounts of data in the URL query string can exceed this limit, leading to truncation or errors (consider a grid/table that takes multiple parameters for filtering, sorting, pagination- all of those params combined might be simply too big for the query params) In that case you might want to either you GET with a request body, or fetch the data with a POST request - which also feels odd ;p

@jonathanmutala8179 4 күн бұрын

why watching this video if i can buy the full course thank you so much for this course

@AzureFullstackDev 4 күн бұрын

thanks for the support :) enjoy the full content

@arunabhtiwari4771 29 күн бұрын

Hi, Thanks for this course. Any new Microservices Webapi course something like any clone with entity framework are aligned up ?

@christian.mar.garcia 3 ай бұрын

Amazing video. Thank you for sharing.

@geepy5708 4 ай бұрын

Nice explanation. I was wondering if you could show an example of what should be in the application layer.

@AzureFullstackDev 4 ай бұрын

stuff like mapping, handling the requests, or even command validation belongs to the application layer, you can have a look at the final project Repo: github.com/jakubkozera/Restaurants or follow along rest of the course on udemy