Repository Pattern | ASP.NET 6 REST API Following CLEAN ARCHITECTURE & DDD Tutorial | Part 3



Repository Pattern | ASP.NET 6 REST API Following CLEAN ARCHITECTURE & DDD Tutorial | Part 3

Repository Pattern | ASP.NET 6 REST API Following CLEAN ARCHITECTURE & DDD Tutorial | Part 3

Link to the full playlist: https://www.youtube.com/watch?v=fhM0V2N1GpY&list=PLzYkqgWkHPKBcDIP5gzLfASkQyTdy0t4k

Become a Patreon & get the source code: https://www.patreon.com/amantinband

Follow me on ’em socials:
Twitter: https://twitter.com/amantinband
LinkedIn: https://www.linkedin.com/in/amantinband/
GitHub: https://github.com/amantinband

What is this series?
We’ll build a REST API following Clean Architecture & Domain-Driven Design principles completely from scratch.
We will use .NET 6, EF Core, and common patterns such as CQRS, unit of work, repository, mediator, and more 💪🏽
We’ll also use some awesome open-source libraries such as MediatR, FluentValidation, ErrorOr, Throw, Mapster, and more.
The developing environment will be visual studio code & dotnet CLI only. We will use awesome vscode plugins for everything from sending HTTP requests to connecting to our SQL database, debugging, and peeking at JWT tokens.
We will code and refactor multiple times to tackle the many concepts I want to teach. When the series will be over, you’ll have a good understanding and intuition on how to use these patterns & libraries in your industry-level applications.

How often will a new part come out?
Once or twice a week.

What are we doing today?
Today’s video is all about the repository pattern: What is it? Should I use it? And why is it so polarizing? We’ll dive deep into the repository pattern, learn about the pros and cons, and implement the user repository in our Buber dinner project, which we’ll use to wire up the register and login endpoints.

#dotnet

Comments are closed.