Resolution:

ActiveSpaces uses memory for each tuple stored in the context of SharedNothing persistence plus eviction. Only the non-indexed portion of a tuple is evicted when the capacity limit is reached. The metadata (tuple information) and indexed portion of the tuple is still held in memory, even if the tuple has been evicted. Shared all persistence will help here. Evicted entries are not kept in memory. When there is a get operation it will be a  cache miss and inquire the database onRead. Users can read tuples from the database. The only disadvantage is that queries cannot return evicted tuples, so you would need to query the database if needed.