Freeze evictors combine persistence and scalability features into a single facility that is easily incorporated into Ice applications.
As an implementation of a servant locator, a Freeze evictor takes advantage of the fundamental separation between Ice object and servant to activate servants on demand from persistent storage, and to deactivate them again using customized eviction constraints. Although an application may have thousands of Ice objects in its database, it is not practical to have servants for all of those Ice objects resident in memory simultaneously. The application can conserve resources and gain greater scalability by setting an upper limit on the number of active servants, and letting a Freeze evictor handle the details of servant activation, persistence, and deactivation.
- Evictor Concepts
- Background Save Evictor
- Transactional Evictor
- Using an Evictor in the File System Server
- Cache Helper Class for Evictor Implementation