What is Repository Pattern in .Net Core - Repository Pattern C#

[@CodingDroplets]

🌟 Get Source Code: www.patreon.com/CodingDroplets 🔗Blazor Tutorial Series: kzbin.info/aero/PLzewa6pjbr3IQEUfNiK2SROQC1NuKl6PV

[@pavanshevle6830]

Your way of teaching is very simple. Thanks. Could you please make video on SOLID principles and different design patterns?

[@CodingDroplets]

Thank you for your kind words! I'm glad you found the tutorial helpful. I appreciate your suggestion, and I'll definitely consider making a video on SOLID principles and different design patterns.

[@imadabab]

This is really perfect. Thanks so much. I have subscribed.

[@CodingDroplets]

Thank you for subscribing! I'm glad you found the tutorial helpful. More content is on the way-stay tuned!

[@sahil100394]

Can you please explain why do we need repository pattern and what are it's alternatives?

[@CodingDroplets]

The repository pattern is a popular approach to organizing your data access code in a way that keeps it clean, maintainable, and testable. It acts as a middle layer between your business logic and the data layer, promoting separation of concerns. Another well-known alternative to this pattern is CQRS (Command Query Responsibility Segregation), which offers a different way to manage your application’s read and write operations.

[@JohnSmith-yr7ih]

Hello and thanks! Please make a tutorial of aspNet web api + Blazor webassembly (not a `BlazorApp` or `Blazor Server` templates) Identity auth tutotial (new way, .net 8). register, login, logout features

[@CodingDroplets]

Thank you for your suggestion! I appreciate your interest. I'll definitely consider creating a tutorial covering those topics

[@WitheredPancake]

Love your videos, but the wobbly text overlays makes me feel dizzy

[@CodingDroplets]

Thank you for the feedback! 😊 I’m glad you're enjoying the videos, and I appreciate your honesty about the text overlays. I’ll definitely keep that in mind for future videos and work on making the visuals smoother. Thanks for watching, and feel free to reach out with any other suggestions!

[@devendrapandey2387]

I don't think this is good approach to create same kind of method again and again for all repository. You can create one Generic repository and inherit that in all others.

[@CodingDroplets]

This video is created to demonstrate how singleton, scoped, and transient lifetimes work in .NET Core. By using this approach, you can clearly see the differences in behavior and values from the same service instance under different lifetimes. For a production application, I agree that creating a generic repository and inheriting it in all others is a better approach for code reuse and maintainability. Thank you for your feedback!

[@imadayoub5237]

Agree with you.