Hi All,
I created a new feature "org.wso2.carbon.hazelcast.feature" as a POC to see
how it should be implemented on top of C5. You can find the code on [1].
In this feature, it initializes a hazelcast instance via the hazelcast.xml
file, which should reside on "[PRODUCT]/conf/hazelcast/", and exp
On a related note, with hazlecast 3.6, the proper OSGi support also
available. We don't need to create an orbit and hazelcast bundle it self
exposes the OSGi service [1]. So this would minimize the maintenance effort
from our side as what we have to do is only write the code needed to
initialize th
On Tue, Feb 9, 2016 at 9:56 AM, Ramith Jayasinghe wrote:
> we are +1 for Hazelcast. we use it main for group communication (and
> member discovery).
>
> On Mon, Feb 8, 2016 at 8:31 PM, Srinath Perera wrote:
> > Moving to arch@
> >
> > CEP ( for Storm based version), MB ( for base algo), ESB ( fo
we are +1 for Hazelcast. we use it main for group communication (and
member discovery).
On Mon, Feb 8, 2016 at 8:31 PM, Srinath Perera wrote:
> Moving to arch@
>
> CEP ( for Storm based version), MB ( for base algo), ESB ( for tasks) are
> known cases. For those, we can use Hazelcast ( they can u
Moving to arch@
CEP ( for Storm based version), MB ( for base algo), ESB ( for tasks) are
known cases. For those, we can use Hazelcast ( they can use it directly).
Hazelcast works OK with small number of nodes. AFAIK, there is no better
solution ( we use Zookeeper before) unless there is somethin
