Hi, I've created SLING-2939 [0] to track an additional, 3rd party based implementation of the discovery.api. The idea is to complement the discovery.impl (which is ootb, entirely sling-based) with a more mature, specialized, scalable implementation based on a clustering library. I've summarized some pros/cons of possible candidates, including some already received feedback in the ticket. I would appreciated further feedback!
It looks like Zookeeper/Curator would be a very good fit, requirement-wise – but there was also an argument for using JGroups (or something like Infinispan ontop of it), although that's LGPL at the moment. At the same time, it might be a good time to discuss if there's any need for api changes, like 'topology-wide leader' or 'grouping/spliting/organizing topologies'. In discussions surrounding topologies, other more consensus-like topics came up (things which zookeeper/curator would cover nicely). The question here is though if that fits into the discovery api itself or if that's not something completely different and out-of-scope of discovery. Thanks, Cheers, Stefan -- [0] - https://issues.apache.org/jira/browse/SLING-2939
