indeXus.Net Shared Cache is high performance distributed and replication cache system build for .Net cache and enterprise application running in server farms.
indeXus.Net Shared Cache provides distributed replicated cache to minimize the load factor on deeper layers. It consists the usage of two or more servers in a farm. It's replicated all data within the cluster. The big plus is simple, you have all your cache nodes on all different servers. In case one of your servers get restarted, it will receive all items automatically from its parent. indeXus.Net Shared Cache uses 100% managed code which is written .Net C#.
Why you should consider to use indeXus.Net Shared Cache? There is no more efficient way to increase the scalable performance of applications then the use caching to unload deeper layers and you able to scale linear.
- We provide a wider range of caching - distributed and replicated caching. The experience we have done so far showed us that a lot of projects have a huge need of data integrity.
- We provide several cleanup models to purge the cache:
a. Cache Item Priority
b. LRU – Least Recent Used Item
c. LFU – Least Frequently Used Item
d. Time based
e. BLF – Biggest Latency First
f. LLF – Lowest Latency First
g. Hybrid – Creating an index based on various item attributes such as: time in cache, Amount of requests, Size, Cache Life Time and some more.
- Configurable maximum cache size and the load factor when the system starts to purge cached items.
- With the upcoming release we gone provide Key Cache Dependency (it can be that in future we will also support SQL and File Dependency)
- With the upcoming release we gone provide bulk operations
- We use a binary format which has an overload payload of 36 bytes per Message.
- Simple server and client configuration with custom provider sections
- We use internally a custom thread pool which is configurable.
- We provide a small management console with some basic information about cache nodes.
- We provide detailed statistic information for client and server:
a. Client Side:
i. Amount of objects which are added / received / removed
ii. Network usage
iii. Successful and failed actions
iv. Item Hit Rate
b. Server Side per Node (all servers are aggregated)
i. Amount of items available
ii. Size of all items
iii. A list with the top 20 keys based on hits
- Last but not least: it’s absolutely free and open source!