CAB from MS is a very famous tool for the developers as it saves a lot of valuable time of the developers. But anyone who has decided to use CAB, should also keep into mind its limitations as well. The cache in EnltLib is stand alone and in-process
in nature that’s why it can ends up with some scalability and reliability issues when used in a multi-server environment. But there are some party integrations which can over come this issue. The most popular way to overcome these limitations of CAB is the
use of a distributed cache. The article about the
drawbacks of CAB and it solutions can be a very helpful read in this regard.
Please mark the replies as answers if they help or unmark if not.
If you have any feedback about my replies, please contact msdnmg@microsoft.com.
Microsoft One Code Framework
None
0 Points
7 Posts
Scale Up Enterprise Library Caching Application Block
May 12, 2011 07:03 AM|wesnur|LINK
CAB from MS is a very famous tool for the developers as it saves a lot of valuable time of the developers. But anyone who has decided to use CAB, should also keep into mind its limitations as well. The cache in EnltLib is stand alone and in-process in nature that’s why it can ends up with some scalability and reliability issues when used in a multi-server environment. But there are some party integrations which can over come this issue. The most popular way to overcome these limitations of CAB is the use of a distributed cache. The article about the drawbacks of CAB and it solutions can be a very helpful read in this regard.
All-Star
24409 Points
3416 Posts
Re: Scale Up Enterprise Library Caching Application Block
May 18, 2011 04:37 AM|Jonathan Shen – MSFT|LINK
Hi Wesnur,
Thanks for your sharing.
If you have any feedback about my replies, please contact msdnmg@microsoft.com.
Microsoft One Code Framework