[
https://issues.apache.org/jira/browse/RATIS-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17053736#comment-17053736
]
Zili Chen commented on RATIS-40:
--------------------------------
[~enis] what is the progress of this feature now? It seems stall for quite a
while, but things changed and I cannot find blockers of this one.
> Replicated Map
> --------------
>
> Key: RATIS-40
> URL: https://issues.apache.org/jira/browse/RATIS-40
> Project: Ratis
> Issue Type: New Feature
> Components: replicated map
> Reporter: Enis Soztutar
> Assignee: Enis Soztutar
> Priority: Major
> Attachments: ratis-40_v1.patch
>
>
> Ratis replicated map is an implementation of a sorted map (think TreeMap) as
> a replicated state machine. This is not under examples because it is intended
> to be used in production where a simple in-memory map is sufficient to hold
> the data. The data is fully cached in memory, but it is still durable since
> raft log is used as a replicated log, and data is snapshotted periodically.
> The replicated map (RMap) is not only the state machine implementation, but
> all of the remaining code, including the client and querying capabilities
> which is built on top of the other modules. In that sense, it is dog-fooding
> the ratis library to implement an end-to-end solution for a replicated
> in-memory data store.
> Replicated maps are conceptually similar to ZooKeeper/Etcd/LogCabin where the
> data is hosted in a known cluster configuration and is not sharded. All the
> servers in the cluster participate in a single RAFT ring.
> The data model is that users can create independent RMap instances in the
> cluster and read / write or scan the data as key value pairs in those
> replicated maps. A replicated map named the meta map contains information
> about all of the other maps in the cluster.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
