Skip to main content

C# : Cached Repository Pattern implementation

 


In modern software development, efficient data access is crucial for maintaining application performance. One way to improve data access performance is by implementing caching mechanisms. In this blog post, we'll explore how to implement the Cached Repository Pattern in C#, a design pattern that combines the benefits of a repository pattern with caching to optimize data access.

What is the Cached Repository Pattern? The Cached Repository Pattern is an architectural pattern that combines the Repository Pattern with caching mechanisms to improve data access performance. It provides a layer of abstraction over data access operations while transparently caching data retrieved from the underlying data source.

Step-by-Step Implementation:

Step 1: Define Repository Interface First, we define an interface that serves as the contract for interacting with the data source. This interface includes methods for common data access operations such as fetching all entities, fetching an entity by ID, adding, updating, and deleting entities.

public interface IDataRepository<T>
{
    IEnumerable<T> GetAll();
    T GetById(int id);
    void Add(T entity);
    void Update(T entity);
    void Delete(int id);
}

Step 2: Implement Concrete Repository Next, we implement a concrete repository class that fulfills the contract defined by the repository interface. This class interacts directly with the underlying data source, such as a database, to perform data access operations.

public class DataRepository<T> : IDataRepository<T>
{
    private readonly DbContext _dbContext;
    private readonly DbSet<T> _dbSet;

    public DataRepository(DbContext dbContext)
    {
        _dbContext = dbContext;
        _dbSet = _dbContext.Set<T>();
    }

    public IEnumerable<T> GetAll()
    {
        return _dbSet.ToList();
    }

    public T GetById(int id)
    {
        return _dbSet.Find(id);
    }

    public void Add(T entity)
    {
        _dbSet.Add(entity);
        _dbContext.SaveChanges();
    }

    public void Update(T entity)
    {
        _dbSet.Update(entity);
        _dbContext.SaveChanges();
    }

    public void Delete(int id)
    {
        var entity = GetById(id);
        if (entity != null)
        {
            _dbSet.Remove(entity);
            _dbContext.SaveChanges();
        }
    }
}

Step 3: Implement Cached Repository Now, we create a cached repository class that wraps the original repository. This cached repository adds caching functionality to the data access operations, transparently caching data retrieved from the underlying data source for improved performance.

public class CachedDataRepository<T> : IDataRepository<T>
{
    private readonly IDataRepository<T> _innerRepository;
    private IEnumerable<T> _cache;

    public CachedDataRepository(IDataRepository<T> innerRepository)
    {
        _innerRepository = innerRepository;
        RefreshCache();
    }

    public IEnumerable<T> GetAll()
    {
        return _cache;
    }

    public T GetById(int id)
    {
        return _cache.FirstOrDefault(item => GetId(item) == id);
    }

    public void Add(T entity)
    {
        _innerRepository.Add(entity);
        RefreshCache();
    }

    public void Update(T entity)
    {
        _innerRepository.Update(entity);
        RefreshCache();
    }

    public void Delete(int id)
    {
        _innerRepository.Delete(id);
        RefreshCache();
    }

    private void RefreshCache()
    {
        _cache = _innerRepository.GetAll();
    }

    private int GetId(T entity)
    {
        // Implement logic to get the ID of the entity
        // For example, if the entity is an object with an "Id" property:
        // return entity.Id;
    }
}

Step 4: Usage Finally, we demonstrate how to use the cached repository in our application to interact with the data source. We instantiate the repository with the appropriate dependencies and utilize its methods to fetch, add, update, and delete entities.

// Usage example
var dbContext = new YourDbContext();
var repository = new DataRepository<YourEntity>(dbContext);
var cachedRepository = new CachedDataRepository<YourEntity>(repository);

// Use the cached repository to fetch data
var data = cachedRepository.GetAll();

Conclusion: The Cached Repository Pattern is a powerful technique for optimizing data access performance in C# applications. By combining the benefits of the Repository Pattern with caching mechanisms, developers can achieve significant improvements in application responsiveness and efficiency. Consider employing this pattern in your next C# project to enhance data access performance and provide a better user experience.


Comments

Popular posts from this blog

Clean Architecture: What It Is and How It Differs from Microservices

In the tech world, buzzwords like   Clean Architecture   and   Microservices   often dominate discussions about building scalable, maintainable applications. But what exactly is Clean Architecture? How does it compare to Microservices? And most importantly, is it more efficient? Let’s break it all down, from understanding the core principles of Clean Architecture to comparing it with Microservices. By the end of this blog, you’ll know when to use each and why Clean Architecture might just be the silent hero your projects need. What is Clean Architecture? Clean Architecture  is a design paradigm introduced by Robert C. Martin (Uncle Bob) in his book  Clean Architecture: A Craftsman’s Guide to Software Structure and Design . It’s an evolution of layered architecture, focusing on organizing code in a way that makes it  flexible ,  testable , and  easy to maintain . Core Principles of Clean Architecture Dependency Inversion : High-level modules s...

C# : How can we access private method outside class

Introduction In object-oriented programming, encapsulation is a fundamental principle that restricts direct access to the internal implementation details of a class. Private methods, being part of this internal implementation, are designed to be accessible only within the confines of the class they belong to. However, there might be scenarios where you need to access a private method from outside the class. In this blog post, we'll explore several techniques to achieve this in C#. 1. Reflection: A Powerful Yet Delicate Approach Reflection is a mechanism in C# that allows inspecting and interacting with metadata about types, fields, properties, and methods. While it provides a way to access private methods, it should be used cautiously due to its potential impact on maintainability and performance. using System ; using System . Reflection ; public class MyClass { private void PrivateMethod ( ) { Console . WriteLine ( "This is a private method."...

20+ LINQ Concepts with .Net Code

LINQ   (Language Integrated Query) is one of the most powerful features in .NET, providing a unified syntax to query collections, databases, XML, and other data sources. Below are 20+ important LINQ concepts, their explanations, and code snippets to help you understand their usage. 1.  Where  (Filtering) The  Where()  method is used to filter a collection based on a given condition. var numbers = new List < int > { 1 , 2 , 3 , 4 , 5 , 6 } ; var evenNumbers = numbers . Where ( n => n % 2 == 0 ) . ToList ( ) ; // Output: [2, 4, 6] C# Copy 2.  Select  (Projection) The  Select()  method projects each element of a sequence into a new form, allowing transformation of data. var employees = new List < Employee > { /* ... */ } ; var employeeNames = employees . Select ( e => e . Name ) . ToList ( ) ; // Output: List of employee names C# Copy 3.  OrderBy  (Sorting in Ascending Order) The  Or...