I think persistence through snapshots (Raul proposed the other day) is an option too. Since all data structures in Ignite are basically key-value, it should be quite universal. Ordering can be preserved too.
#This will also require taking care of data updated between snapshots to avoid data loss in case of a cluster-wide failure. -Roman On Friday, January 15, 2016 4:32 PM, Valentin Kulichenko <[email protected]> wrote: Igniters, It sounds like users could be interested in being able to persist the data saved in queues and sets. See the thread on user list [1]. The obvious solution is to reuse our CacheStore interface, but I'm not sure that this is possible because it's designed for key-value storage. E.g., what is the key for a set element? In case of a queue we also need to be able to preserve order after writing to the database and reloading. Any ideas how to achieve this? -Val [1] http://apache-ignite-users.70518.x6.nabble.com/Stupide-question-about-Queue-td2557.html
