Hi all, We had a discussion on the same and decided to use some broker-based notification service for this. IIRC Sanjeewa was working on this.
Thanks, Senaka. On Sat, Oct 19, 2013 at 10:18 AM, Sanjiva Weerawarana <[email protected]>wrote: > (Removed private list.) > > +1 .. caching across product clusters is a different problem and best > solved by a common service. > > Sanjiva. > > > On Sat, Oct 19, 2013 at 1:39 AM, Afkham Azeez <[email protected]> wrote: > >> If we need cross product caching, we would need a caching service... >> something similar to AWS Elasticache. >> >> >> On Sat, Oct 19, 2013 at 1:28 AM, Afkham Azeez <[email protected]> wrote: >> >>> Cache replication is within the cluster only. Replication does not scale >>> across multiple clusters. >>> >>> >>> On Fri, Oct 18, 2013 at 11:13 PM, Chris Haddad <[email protected]> wrote: >>> >>>> So ah, err... what is the viable use cases for our cache? I thought >>>> the cache was at the Carbon framework level, and therefore spanned >>>> products. >>>> >>>> If I create a cache entry in an AppServer cluster, is cache entry scope >>>> all application server instances, but not all UES cluster instances? Do >>>> we restrict session replication to only a single product, even though all >>>> products live on the same platform foundation? >>>> >>>> >>>> If I create a cache entry in a Stratos 2.0 cartridge (i.e. >>>> getCurrentContext.getCache().put), what is the cache entry scope? Within >>>> tenant usage of all similar cartridges (i.e. tenant-cartridge >>>> subscription), or all cartridges used by the tenant? >>>> >>>> >>>> >>>> >>>> On Wed, Oct 16, 2013 at 11:36 PM, Eranda Sooriyabandara < >>>> [email protected]> wrote: >>>> >>>>> Hi Harsha, all, >>>>> >>>>> Should we look at the possibility to give a feature to clear cache >>>>>> among the cross product cluster using hazlecast when it share >>>>>> common registry. In stratos 1.6, it shares governance registry among the >>>>>> cross product with tribes without having that cache clear feature among >>>>>> the >>>>>> cross product cluster. >>>>>> >>>>> >>>>> >>>>> This is a problem we have with our platform, though we have the story >>>>> of having shared registry we don't have a clear defined way of >>>>> communicating between those nodes to invalidate the resource cache. I am >>>>> not sure whether the hazelcast it self should be the communication handler >>>>> but our registry sharing is incomplete without it. We had this discussion >>>>> some times back but still we are in no-solution state. >>>>> >>>>> thanks >>>>> Eranda >>>>> >>>>> >>>>> >>>>>> >>>>>> thanks >>>>>> >>>>>> *Harsha Thirimanna* >>>>>> Senior Software Engineer; WSO2, Inc.; http://wso2.com >>>>>> * <http://www.apache.org/>** >>>>>> email: **[email protected]* <[email protected]>* cell: +94 71 5186770** >>>>>> twitter: **http://twitter.com/ <http://twitter.com/afkham_azeez>** >>>>>> harshathirimann >>>>>> linked-in: **http: <http://lk.linkedin.com/in/afkhamazeez>**// >>>>>> www.linkedin.com/pub/harsha-thirimanna/10/ab8/122* >>>>>> * >>>>>> * >>>>>> *Lean . Enterprise . Middleware* >>>>>> * >>>>>> * >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> *Eranda Sooriyabandara >>>>> *Senior Software Engineer; >>>>> Integration Technologies Team; >>>>> WSO2 Inc.; http://wso2.com >>>>> Lean . Enterprise . Middleware >>>>> >>>>> E-mail: eranda AT wso2.com >>>>> Mobile: +94 716 472 816 >>>>> Linked-In: http://www.linkedin.com/in/erandasooriyabandara >>>>> Blog: http://emsooriyabandara.blogspot.com/ >>>>> >>>>> >>>>> >>>>> * >>>>> * >>>>> >>>> >>>> >>>> >>>> -- >>>> +1.678.431.1656 >>>> mailto:[email protected] >>>> twitter @cobiacomm >>>> http://blog.cobia.net/cobiacomm (blog) >>>> >>>> >>> >>> >>> -- >>> *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* >>> >> >> >> >> -- >> *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* >> > > > > -- > 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 > > -- * <http://us13.wso2con.com/> * * * *Senaka Fernando* Senior Technical Lead; WSO2 Inc.; http://wso2.com* Member; Apache Software Foundation; http://apache.org E-mail: senaka AT wso2.com **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://linkedin.com/in/senakafernando *Lean . Enterprise . Middleware
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
