Azeez don't we need the management API in worker nodes? I assume the answer is yes ..
So in that case the worker contains the runtime container logic plus a management API (running at a separate port etc. and enabled by request). The management node contains an admin app that talks to the worker nodes via the API and other means (such as ADC). Right? +1 as long as we can still ship a multi-profile distro by default where all of this is in one JVM and then you give the personalty at boot time. Sanjiva. On Thu, Mar 21, 2013 at 6:03 PM, Afkham Azeez <[email protected]> wrote: > > > On Thu, Mar 21, 2013 at 5:56 PM, Samisa Abeysinghe <[email protected]>wrote: > >> >> >> On Thu, Mar 21, 2013 at 3:35 PM, Afkham Azeez <[email protected]> wrote: >> >>> With the worker-manager concept, we no longer require FE-BE separation. >>> There is no need to have FE-BE separation for the management node. So, I >>> think we can completely do away with that concept. >> >> >> But how do we separate the worker stuff from manager stuff? >> Is that not >> Manger == FE + BE >> Worker == BE >> >> > > No, FE is the front end of the management admin client. BE is the > management service/API. Worker provides the runtime to run services, apps, > processes, mediation etc. We have made the mistake of calling this runtime > as BE as well. Management nodes will not ideally require this runtime, but > we may need to have some parts of it. e.g. validating the Synapse config > will require Synapse to be in the management node. We will never have a > case where a FE talks to a BE in a worker node. When it comes to the mgt > node, there is no need for separating the FE & BE. > > >> >>> What do you guys think? >>> >>> -- >>> *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 >>> >>> Thanks, >> Samisa... >> >> Samisa Abeysinghe >> VP Engineering >> WSO2 Inc. >> http://wso2.com >> http://wso2.org >> >> >> >> _______________________________________________ >> 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* > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- 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
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
