Currently MB needs a Cassandra to function. (Even is in-memory mode, subscriptions are kept in Cassandra).
So we need to do some work to reduce the footprint. --Srinath On Fri, Sep 13, 2013 at 5:17 PM, Senaka Fernando <[email protected]> wrote: > Hi all, > > To add to this, there was a concern on the footprint of MB running inside > carbon servers. And, as discussed MB+Cassandra is not what's going to be > used here, but probably another mode. There will be 3 modes in total: > > 1. In-memory > 2. SQL-DB > 3. Cassandra > > The Embedded-MB will be like an Embedded Registry or AM, and will be a > minimal deployment to support basic requirements. Further, MB is not simply > used for DepSync but also for several platform-wide requirements and as a > part of the unification process we are working on. For example, > Notifications will use this too. > > Thanks, > Senaka. > > > > On Fri, Sep 13, 2013 at 5:06 PM, Pradeep Fernando <[email protected]>wrote: > >> Hi All, >> >> During the recent depsync related meeting, the above $subject came up.. >> here are the some of the discussion points. >> >> - Currently our depsync setup uses cluster messages to send the >> repository sync message >> - Message loss is a one issue with the current approach. message >> replaying can be done, but not the proper way to do it. >> - We can use JMS/MB as the communication mechanism between depsync nodes. >> - the solution scales well, message persistence is there by default. >> >> Approach, >> >> - We ship a embedded MB server with our every product. (p2 feature >> installation is one/server profile/ etc is open for discussion) >> - manager node starts up the MB server, worker nodes read from it. >> - LB can load balance across cluster either using static endpoints or can >> get the endpoint details from the MB itself - LB doe not have to use >> clustering anymore.. >> >> >> Concerns, >> >> How are we going to incoperate these changes to future releases. >> Deployment is part of the carbon kernel. If we are to implement above there >> are kernel changes. what is the expected release version, >> >> thanks, >> --Pradeep >> > > > > -- > * <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 > -- ============================ Srinath Perera, Ph.D. Director, Research, WSO2 Inc. Visiting Faculty, University of Moratuwa Member, Apache Software Foundation Research Scientist, Lanka Software Foundation Blog: http://srinathsview.blogspot.com/ Photos: http://www.flickr.com/photos/hemapani/ Phone: 0772360902
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
