Hi All,
On Fri, Sep 13, 2013 at 4:36 AM, 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. > Say that we have multiple manager nodes, then how this will work? Thanks, Kishanthan. - 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 > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- *Kishanthan Thangarajah* Senior Software Engineer, Platform Technologies Team, WSO2, Inc. lean.enterprise.middleware Mobile - +94773426635 Blog - *http://kishanthan.wordpress.com* Twitter - *http://twitter.com/kishanthan*
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
