Unlike Tribes, Hazelcast has been designed to scale on the cloud. All the cluster messaging related issues we were seeing were due to Tribes, and Tribes was designed only for datacenter scale.
Azeez On Tue, Sep 17, 2013 at 9:49 AM, Sanjiva Weerawarana <[email protected]>wrote: > I don't see the point of marrying into Hazelcast at that level. The > problem required here is a queuing solution because we need it to scale > from simple to very large installations involving multiple AZs etc.. Many > times persistent reliability is important (esp for deployment messages). > Why would we re-invent all of that on top of Hazelcast instead of using MB? > Of course we need an embedded, in-memory, ultra-light weight system too for > the simple case and MB can deliver that quite easily. > > Sanjiva. > > > On Tue, Sep 17, 2013 at 12:07 AM, Afkham Azeez <[email protected]> wrote: > >> >> >> >> On Mon, Sep 16, 2013 at 11:42 PM, Afkham Azeez <[email protected]> wrote: >> >>> >>> >>> >>> On Mon, Sep 16, 2013 at 11:20 PM, Isuru Perera <[email protected]> wrote: >>> >>>> >>>> >>>> >>>> On Mon, Sep 16, 2013 at 8:05 PM, Afkham Azeez <[email protected]> wrote: >>>> >>>>> >>>>> >>>>> >>>>> On Mon, Sep 16, 2013 at 7:17 PM, Afkham Azeez <[email protected]> wrote: >>>>> >>>>>> With the new Hazelcast based clustering implementation, in fact, >>>>>> cluster messaging is done using a Hazelcast topic the same pub/sub >>>>>> semantics. So, do we really need to use MB? >>>>>> >>>>>> What are the advantages of MB compared to Hazelcast topics? >>>>>> >>>>> >>>>> Another aspect to think about is that for MB in memory mode, in the >>>>> future, we could end up using Hazelcast topics/queues. If so, shifting >>>>> from >>>>> cluster messaging to MB would not make that much of a difference. >>>>> >>>> Yes! If we can overcome current DepSync issues with Hazelcast, there >>>> will be no point in going for an MB. >>>> >>> >>> >>> What are the current Hazelcast related depsync issues? >>> >>> >> Please let us know if there are any Hazelcast related issues, because we >> could easily get help from the Hz devs. >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > Sanjiva Weerawarana, Ph.D. > Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ > email: [email protected]; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 > 650 265 8311 > blog: http://sanjiva.weerawarana.org/ > > Lean . Enterprise . Middleware > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * <http://www.apache.org/>** email: **[email protected]* <[email protected]>* cell: +94 77 3320919 blog: **http://blog.afkham.org* <http://blog.afkham.org>* twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware*
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
