search

evilsquirr3l / eShop

2 stars 3 forks source link

Add ASP NET Core caching #83

Open Bubasick opened 2 years ago

Bubasick commented 2 years ago

If new products are not added often (by often I mean there can be an hour difference between entries) consider using caching with AWS CloudFront

evilsquirr3l commented 2 years ago

Cloudfront is used to cache in the nearest edge point of the current user. It means that if we had Australian customers, but the server was in Europe, then it would make sense. But if you think about eShop like about diploma project, Cloudfront is pointless and it can lead to wasting money on what we actually don't need.

Bubasick commented 2 years ago

I thought we don't think of this project as a diploma one, because noone will use it for their diploma. I see this project as a ground to implement stuff you are interested in. Also about this one

Cloudfront is used to cache in the nearest edge point of the current user. It means that if we had Australian customers, but the server was in Europe, then it would make sense

Please elaborate about the impact of the location server/user that you mentioned. Cache will allow us to save computing time by not making all the filtering operations per request, also there will be a significant relief on the db connection troughoutput

evilsquirr3l commented 2 years ago

So how about doing this for free https://docs.microsoft.com/en-us/aspnet/core/performance/caching/response?view=aspnetcore-6.0 instead of adding cloudfront for $$$?

Bubasick commented 2 years ago

Hmm, saving some sweet juicy $$$ is always a priority. I think this is worth investigation. Like performance/cost of response caching and performance/cost with cloudfront. Then we'll can pick which one we want.