redis - Asp.net Session or Distributed Cache - which is viable solution

Question

We have MVC 4 application which communicates with backend D365 entities. The application makes a lot of CRM calls to get the data hence it was really slow and the user experience was very poor

To improve its performance, cache layer has been added and whenever application gets a data from CRM, it puts it into Session variable.

Surely, that helped with the performance as within the user's session , it prevents the trip to server and everything is served from session data. However now the application is having a lot of data syncing issues. (data saved by one user is not reflected to others until they logout and re-login)

My questions : was it really a good way of handling the performance issue the application was having? In my opinion, rather then fixing the performance issue , a workaround was added which becomes the cause of other issue.

secondly question: is there a better architecture/design that can be put in place which will improve the performance as well as resolve the data syncing issues the application is having? I am thinking to add a distributed cache layer (Azure Redis likely) to replace in-place Session layer, and optionally (if that makes sense) to implement write-through strategy in Redis so that the front-end application only talks to Cache and let cache keep the data store up to date.

Any guidance or pointer is very much appreciated!

Answer 1

等待大神答复