Become a .NET & Blazor expert with weekly tutorials featuring best practices and the latest improvements, right in your inbox.
Blazor's New Web App Template🔥, Deepen Your Repository Pattern Knowledge🚀
Hey Reader,
The recent release of .NET 8's RC1 brought us an exciting Blazor Web App Template that combines both Blazor Server and WebAssembly in a single project. In my latest video, I dive into this template, highlighting the new render modes of Blazor in .NET 8.
Additionally, I wanted to share an intriguing Q&A from our .NET Web Academy Community this week about enhancing repositories as applications grow. Paolo asked:
"Hi Patrick, sometimes it is necessary to work on several Domain Entities at the same time and the single-entity CRUD offered by Repositories is not sufficient. Thinking of combining in a 2nd level Repository, which uses single-entity repositories is sometimes not possible and often creates a performance decay. What is your suggestion?"
My response:
"Hi Paolo,
Thank you for your insightful question. As our applications grow, it’s essential to address architectural concerns to balance flexibility, maintainability, and performance. Let’s dive deeper into the solutions with a mix of simple theoretical insight and code examples tailored to our .NET Web Academy’s project.
Aggregate Roots:
Think of an Aggregate Root as a main item that groups related things together. By working with this main item, we can easily manage the related items without messing things up.
Example: In our TimeTracker, a Project can be seen as the main item that has linked TimeEntry and ProjectDetails. So, if we want to make changes to a TimeEntry for a project, we go through the Project.
Specification Pattern:
This is a way to set rules for fetching specific items from our data. It’s super useful when we have a lot of rules!
Example: Instead of multiple methods to get data, we use rules. Like one that fetches all time entries for a project.
UnitOfWork Pattern:
It’s like a safety net. When we have multiple changes to save, it ensures all changes are saved correctly or none at all.
Example: If we’re updating a Project and its TimeEntry, this ensures both updates are done right.
Performance Tips:
As our app grows, it’s important to fetch data quickly. There are ways to do this effectively.
Example: Using Entity Framework, we can fetch a Project and its TimeEntries together, which is faster.
Custom Repositories:
Sometimes, we need special methods to get or update our data.
Example: A method that gets a Project, its TimeEntries, and ProjectDetails all together.
In short, as we handle more data, we might need to mix and match different techniques to make things easier and faster. Your question helps us all think deeper about these challenges."
📩 Have a burning question or a topic on your mind? Simply hit 'reply' and send it my way. I genuinely appreciate your feedback and ensure I read every message.
Until next time, happy coding! 💻
Take care,
Patrick
Patrick God
Become a .NET & Blazor expert with weekly tutorials featuring best practices and the latest improvements, right in your inbox.
Hey Reader, You sit down to build an API, add some authentication, and think, “JWT should do the trick.” But then you wonder: What happens if my JWT gets stolen? How do I keep users logged in without compromising security? Sound familiar? In my latest video, I show you how to implement secure JWT authentication with short-lived tokens and refresh tokens in .NET. This setup minimizes risk while keeping the user experience seamless. No fluff - just practical, real-world guidance for building...
Hey Reader, Tired of factories and messy if-else logic in your projects? Since .NET 8, Keyed Services make it easy to handle multiple implementations. No more clutter - just clean, scalable code. In my new video, you’ll see how to dynamically pick services using a key and write code that’s easy to extend. It’s a fresh, modern approach to dependency injection that’ll have you rethinking how you design your APIs. 👉 Watch the video here Wishing you a fantastic start to the new year filled with...
Hey Reader, You sit down to write an API, and before you know it, you’re knee-deep in controllers, attributes, and boilerplate. Sound familiar? What if you could skip all that and still build a fully functional API - fast? That’s where Minimal APIs in .NET come in. They’re clean and lightweight and make building APIs feel like a breeze. In my latest video, I show you how to set up endpoints step by step and structure everything neatly so your code stays easy to read and scale. No fluff - just...