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

Posted to issues@ratis.apache.org by "Niels Basjes (JIRA)" <ji...@apache.org> on 2017/04/25 07:03:04 UTC

[jira] [Created] (RATIS-79) Create Apache Curator for Ratis.

Niels Basjes created RATIS-79:
---------------------------------

             Summary: Create Apache Curator for Ratis.
                 Key: RATIS-79
                 URL: https://issues.apache.org/jira/browse/RATIS-79
             Project: Ratis
          Issue Type: Wish
            Reporter: Niels Basjes


A few weeks ago I attended the presentation in Munich about Ratis.
I had an idea on how the adoption of Ratis can be improved.

Apache Curator makes using zookeeper easy.
So if a development team only has to change a dependency (so instead of curator use raftcurator) and with as few code changes as possible they can experiment with raft. Then the switching cost of a project will go down a lot and the probability of switching increases.

So my proposal is: Make a wrapper/library that is a 100% drop in replacement for Apache Curator. All externally facing package names, classnames and methods are 'the same' and behave 'the same'.

P.S. Perhaps this ticket should be implemented at the curator end instead of here. I let you decide.





--
This message was sent by Atlassian JIRA
(v6.3.15#6346)