You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Sergey Chugunov (Jira)" <ji...@apache.org> on 2021/12/29 15:24:00 UTC

[jira] [Created] (IGNITE-16232) PageMemory Persistent Store porting and refactoring

Sergey Chugunov created IGNITE-16232:
----------------------------------------

             Summary: PageMemory Persistent Store porting and refactoring
                 Key: IGNITE-16232
                 URL: https://issues.apache.org/jira/browse/IGNITE-16232
             Project: Ignite
          Issue Type: Epic
          Components: persistence
            Reporter: Sergey Chugunov


Ignite 2.x storage based on PageMemory shows good performance on read-intensive workloads and can be used both in in-memory and persistent scenarios.

So it can be employed in Ignite 3.0 for use-cases where RocksDB is less effective.

At the same time Ignite 3.0 already has Raft-based replication protocol which can provide logging service for PageMemory-based storage.
This allows implementing more efficient and reliable algorithms of logging and checkpointing.

A more detailed overview of these algorithms is available in [this document|https://github.com/apache/ignite-3/blob/ignite-14647/modules/vault/README.md].



--
This message was sent by Atlassian Jira
(v8.20.1#820001)