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 exposes the hazelcast instance to the rest of the carbon components via "CarbonHazelcastAgent". [1] https://github.com/wso2/carbon-kernel/tree/hamming-release-poc/modules/carbon-hazelcast Thanks Jayanga. *Jayanga Dissanayake* Senior Software Engineer WSO2 Inc. - http://wso2.com/ lean . enterprise . middleware email: [email protected] mobile: +94772207259 On Tue, Feb 9, 2016 at 2:28 PM, Kishanthan Thangarajah <[email protected]> wrote: > 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 the hazelcast instance (and also add the leader election > implementation logic). > > Also we can use the hazelcast.xml as the configuration file rather than > creating a new one. > > Thanks, > Kishanthan. > [1] > https://github.com/hazelcast/hazelcast/blob/master/hazelcast/src/main/java/com/hazelcast/osgi/impl/Activator.java > > On Tue, Feb 9, 2016 at 10:00 AM, Kasun Indrasiri <[email protected]> wrote: > >> >> >> On Tue, Feb 9, 2016 at 9:56 AM, Ramith Jayasinghe <[email protected]> >> 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 <[email protected]> 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 use it >>> directly). >>> > >>> >> >> Yeah, in ESB we used it for Polling Inbound endpoints (JMS, VFS etc.), >> Message Processor coordination and Scheduled Task coordination (the >> underlying implementation is based on ntasks). >> Regarding the # of nodes, say if we have few hundreds of nodes which >> requires coordination for aforementioned functionality, I guess Hazelcast >> still can gracefully handle that use case too. >> >>> > Hazelcast works OK with small number of nodes. AFAIK, there is no >>> better >>> > solution ( we use Zookeeper before) unless there is something new. >>> > >>> > --Srinath >>> > >>> > >>> > >>> > On Mon, Feb 8, 2016 at 8:07 PM, Sameera Jayasoma <[email protected]> >>> wrote: >>> >> >>> >> Looks like several products require distributed coordination. We need >>> to >>> >> evaluate these requirements and come up with a solution. >>> >> >>> >> Hazelcast is used in C4 based products to achieve distributed >>> >> coordination. Not sure whether we should go ahead with Hazelcast >>> after all >>> >> the issues we've faced so far with it. >>> >> >>> >> Kasun, Ramith and Suho can you guys explain the requirement to use the >>> >> distributed coordination. >>> >> >>> >> >> Thanks, >>> >> Sameera. >>> >> >>> > >>> >>> >>> >>> -- >>> Ramith Jayasinghe >>> Technical Lead >>> WSO2 Inc., http://wso2.com >>> lean.enterprise.middleware >>> >>> E: [email protected] >>> P: +94 777542851 >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >> >> >> >> -- >> Kasun Indrasiri >> Software Architect >> WSO2, Inc.; http://wso2.com >> lean.enterprise.middleware >> >> cell: +94 77 556 5206 >> Blog : http://kasunpanorama.blogspot.com/ >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > *Kishanthan Thangarajah* > Associate Technical Lead, > Platform Technologies Team, > WSO2, Inc. > lean.enterprise.middleware > > Mobile - +94773426635 > Blog - *http://kishanthan.wordpress.com <http://kishanthan.wordpress.com>* > Twitter - *http://twitter.com/kishanthan <http://twitter.com/kishanthan>* >
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
