-
|
Hi everyone, I’ve been discussing with my team the potential benefits of using the AWS .NET Distributed Cache Provider instead of querying DynamoDB directly in our application. We are currently using DynamoDB as our main data store, and we're evaluating whether introducing the distributed cache layer would bring significant performance or scalability advantages. Could someone help clarify in what scenarios it would be better to use the AWS .NET Distributed Cache Provider? Are there any best practices or common pitfalls we should be aware of when making this architectural decision? Thanks in advance for your insights! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Using our distributed library allows integrating DynamoDB as the backing store whenever you are using ASP.NET Core's distributed cache framework. This is generally used for temporary caches not for application data stores. Storing session state is a common example for using the distributed cache framework of ASP.NET Core. If you are talking about your application's business data store I would expect you to work with the DynamoDB SDK directly and not the cache framework for temporal data. |
Beta Was this translation helpful? Give feedback.
Using our distributed library allows integrating DynamoDB as the backing store whenever you are using ASP.NET Core's distributed cache framework. This is generally used for temporary caches not for application data stores. Storing session state is a common example for using the distributed cache framework of ASP.NET Core.
If you are talking about your application's business data store I would expect you to work with the DynamoDB SDK directly and not the cache framework for temporal data.