Tiered Storage offers an extension to Hazelcast map, which allows you to store a larger data set than available memory.
|If your Enterprise license was generated before Hazelcast Platform version 5.2, you’ll need a new Enterprise license that enables Tiered Storage. See Managing Enterprise License Keys.|
What Can You Do with Tiered Storage?
Have fewer Hazelcast members for large maps: If you have a map with 1TB of data, you may need around 10 Hazelcast members if all data is kept in the memory, With Tiered Storage, you would need one or two members depending on your cluster’s availability needs.
Size-comfortable SQL operations: When you do table joins in SQL, the intermediate result may become too large to fit in the memory; with Tiered Storage this is not an issue.
How Does Tiered Storage Work?
Tiered Storage uses the following:
An in-memory index to allow faster access to map entries.
A special memory manager to decide which entries to store in the memory tier or the disk tier. If a map entry is not accessed for some time, it gets flushed to the disk. If a map is frequently accessed, it stays in memory.