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..
>

Using static endpoints is not suiting for a scaling dynamic environment. In
the case of having our ELB, we could create a topic per a cluster within
ELB and then let nodes subscribe to the well known ELB's matching topic.

If there's no LB involved, one mgt node can create a topic which
corresponds to its domain and then let other nodes subscribe to this Well
known topic.

>
>
> 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
>
>


-- 

Thanks & regards,
Nirmal

Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to