|
| 1 | +# Entity Cache |
| 2 | + |
| 3 | +ABP Framework provides **Distributed Entity Caching System** for caching entities. |
| 4 | + |
| 5 | +You can use this caching mechanism if you want to cache your entity objects automatically and retrieve them from a cache instead of querying it from a database repeatedly. |
| 6 | + |
| 7 | +## How Distributed Entity Caching System Works? |
| 8 | + |
| 9 | +ABP's Entity Caching System does the following operations on behalf of you: |
| 10 | + |
| 11 | +* It gets the entity from the database (by using the [Repositories](Repositories.md)) in its first call and then gets from the cache in subsequent calls. |
| 12 | +* It automatically invalidates the cached entity if the entity is updated or deleted. Thus, it will be retrieved from the database in the next call and will be re-cached. |
| 13 | +* It uses the cache class's **FullName** as a cache name by default. You can use the `CacheName` attribute on the cache item class to set the cache name. |
| 14 | + |
| 15 | +## Installation |
| 16 | + |
| 17 | +[Volo.Abp.Caching](https://www.nuget.org/packages/Volo.Abp.Caching) is the main package for the ABP's caching system and it's already installed in [the application startup template](Startup-Templates/Index.md). So, you don't need to install it manually. |
| 18 | + |
| 19 | +## Usage |
| 20 | + |
| 21 | +`IEntityCache<TEntityCacheItem, TKey>` is a simple service provided by the ABP Framework for caching entities. It's designed as read-only and contains two methods: `FindAsync` and `GetAsync`. |
| 22 | + |
| 23 | +### Caching Entities |
| 24 | + |
| 25 | +**Example: `Product` entity** |
| 26 | + |
| 27 | +```csharp |
| 28 | +[CacheName("Products")] |
| 29 | +public class Product : AggregateRoot<Guid> |
| 30 | +{ |
| 31 | + public string Name { get; set; } |
| 32 | + public string Description { get; set; } |
| 33 | + public float Price { get; set; } |
| 34 | + public int StockCount { get; set; } |
| 35 | +} |
| 36 | +``` |
| 37 | + |
| 38 | +* This example uses the `CacheName` attribute for the `Product` class to set the cache name. By default, the cache class's **FullName** is used for the cache name. |
| 39 | + |
| 40 | +If you want to cache this entity, first you should configure the [dependency injection](Dependency-Injection.md) to register the `IEntityCache` service in the `ConfigureServices` method of your [module class](Module-Development-Basics.md): |
| 41 | + |
| 42 | +```csharp |
| 43 | +context.Services.AddEntityCache<Product, Guid>(); |
| 44 | +``` |
| 45 | + |
| 46 | +Then configure the [object mapper](https://docs.abp.io/en/abp/latest/Object-To-Object-Mapping) (for `Product` to `ProductDto` mapping): |
| 47 | + |
| 48 | +```csharp |
| 49 | +public class MyProjectNameAutoMapperProfile : Profile |
| 50 | +{ |
| 51 | + public MyProjectNameAutoMapperProfile() |
| 52 | + { |
| 53 | + //other mappings... |
| 54 | +
|
| 55 | + CreateMap<Product, ProductDto>(); |
| 56 | + } |
| 57 | +} |
| 58 | +``` |
| 59 | + |
| 60 | +Now you can inject the `IEntityCache<Product, Guid>` service wherever you need: |
| 61 | + |
| 62 | +```csharp |
| 63 | +public class ProductAppService : ApplicationService, IProductAppService |
| 64 | +{ |
| 65 | + private readonly IEntityCache<Product, Guid> _productCache; |
| 66 | + |
| 67 | + public ProductAppService(IEntityCache<Product, Guid> productCache) |
| 68 | + { |
| 69 | + _productCache = productCache; |
| 70 | + } |
| 71 | + |
| 72 | + public async Task<ProductDto> GetAsync(Guid id) |
| 73 | + { |
| 74 | + var product = await _productCache.GetAsync(id); |
| 75 | + return ObjectMapper.Map<Product, ProductDto>(product); |
| 76 | + } |
| 77 | +} |
| 78 | +``` |
| 79 | + |
| 80 | +* Here, we've directly cached the `Product` entity. In that case, the `Product` class must be serializable. Sometimes this might not be possible and you may want to use another class to store the cache data. For example, we may want to use the `ProductDto` class instead of the `Product` class for the cached object if the `Product` entity is not serializable. |
| 81 | + |
| 82 | +### Caching Cache Item Classes |
| 83 | + |
| 84 | +`IEntityCache<TEntity, TEntityCacheItem, TKey>` service can be used for caching other cache item classes if the entity is not serializable. |
| 85 | + |
| 86 | +**Example: `ProductDto` class** |
| 87 | + |
| 88 | +```csharp |
| 89 | +public class ProductDto : EntityDto<Guid> |
| 90 | +{ |
| 91 | + public string Name { get; set; } |
| 92 | + public string Description { get; set; } |
| 93 | + public float Price { get; set; } |
| 94 | + public int StockCount { get; set; } |
| 95 | +} |
| 96 | +``` |
| 97 | + |
| 98 | +Register the entity cache services to [dependency injection](Dependency-Injection.md) in the `ConfigureServices` method of your [module class](Module-Development-Basics.md): |
| 99 | + |
| 100 | +```csharp |
| 101 | +context.Services.AddEntityCache<Product, ProductDto, Guid>(); |
| 102 | +``` |
| 103 | + |
| 104 | +Configure the [object mapper](https://docs.abp.io/en/abp/latest/Object-To-Object-Mapping) (for `Product` to `ProductDto` mapping): |
| 105 | + |
| 106 | +```csharp |
| 107 | +public class MyProjectNameAutoMapperProfile : Profile |
| 108 | +{ |
| 109 | + public MyProjectNameAutoMapperProfile() |
| 110 | + { |
| 111 | + //other mappings... |
| 112 | +
|
| 113 | + CreateMap<Product, ProductDto>(); |
| 114 | + } |
| 115 | +} |
| 116 | +``` |
| 117 | + |
| 118 | +Then, you can inject the `IEntityCache<ProductDto, Guid>` service wherever you want: |
| 119 | + |
| 120 | +```csharp |
| 121 | +public class ProductAppService : ApplicationService, IProductAppService |
| 122 | +{ |
| 123 | + private readonly IEntityCache<ProductDto, Guid> _productCache; |
| 124 | + |
| 125 | + public ProductAppService(IEntityCache<ProductDto, Guid> productCache) |
| 126 | + { |
| 127 | + _productCache = productCache; |
| 128 | + } |
| 129 | + |
| 130 | + public async Task<ProductDto> GetAsync(Guid id) |
| 131 | + { |
| 132 | + return await _productCache.GetAsync(id); |
| 133 | + } |
| 134 | +} |
| 135 | +``` |
| 136 | + |
| 137 | +## Configurations |
| 138 | + |
| 139 | +### Registering the Entity Cache Services |
| 140 | + |
| 141 | +You can use one of the `AddEntityCache` methods to register entity cache services to the [Dependency Injection](Dependency-Injection.md) system. |
| 142 | + |
| 143 | +```csharp |
| 144 | +public override void ConfigureServices(ServiceConfigurationContext context) |
| 145 | +{ |
| 146 | + var configuration = context.Services.GetConfiguration(); |
| 147 | + |
| 148 | + //other configurations... |
| 149 | +
|
| 150 | + //directly cache the entity object (Basket) |
| 151 | + context.Services.AddEntityCache<Basket, Guid>(); |
| 152 | + |
| 153 | + //cache the ProductDto class |
| 154 | + context.Services.AddEntityCache<Product, ProductDto, Guid>(); |
| 155 | +} |
| 156 | +``` |
| 157 | + |
| 158 | +* You can register entity cache by using the `context.Services.AddEntityCache<TEntity, TKey>()` method for directly cache the entity object. |
| 159 | +* Or alternatively, you can use the `context.Services.AddEntityCache<TEntity, TEntityCacheItem, TKey>()` method to configure entities that are mapped to a cache item. |
| 160 | + |
| 161 | +### Caching Options |
| 162 | + |
| 163 | +All of the `context.Services.AddEntityCache()` methods get an optional `DistributedCacheEntryOptions` parameter where you can easily configure the caching options: |
| 164 | + |
| 165 | +```csharp |
| 166 | +context.Services.AddEntityCache<Product, ProductDto, Guid>( |
| 167 | + new DistributedCacheEntryOptions |
| 168 | + { |
| 169 | + SlidingExpiration = TimeSpan.FromMinutes(30) |
| 170 | + } |
| 171 | +); |
| 172 | +``` |
| 173 | + |
| 174 | +> The default cache duration is **2 minutes** with the `AbsoluteExpirationRelativeToNow` configuration and by configuring the `DistributedCacheEntryOptions` you can change it easily. |
| 175 | +
|
| 176 | +## Additonal Notes |
| 177 | + |
| 178 | +* Entity classes should be serializable/deserializable to/from JSON to be cached (because it's serialized to JSON when saving in the [Distributed Cache](Caching.md)). If your entity class is not serializable, you can consider using a cache-item/DTO class instead, as mentioned in the *Usage* section above. |
| 179 | +* Entity Caching System is designed as **read-only**. So, you shouldn't make changes to the same entity when you use the entity cache. Instead, you should always read it from the database to ensure transactional consistency. |
| 180 | + |
| 181 | +## See Also |
| 182 | + |
| 183 | +* [Caching](Caching.md) |
0 commit comments