On Wed, Jan 15, 2014 at 11:58 PM, Manuranga Perera <[email protected]> wrote:
> Current implementation (correct me if I am wrong): > In Hazalcast clustering implementation, different ports are used for each > cluster. This is to stop clutter a single port which was not a scalable > solution. > No. Same port different domains work fine. > > My question: > Can we get the same (or almost same) benefit by using the same port, but > putting each cluster in a different Hazalcast group? > > Reason: > In AWS like deployment, opening up ports and managing them with each > server start-up takes a significant effort on the infrastructure side. So > if this can be avoided without much adverse effect it would be worth > considering. > > -- > With regards, > *Manu*ranga Perera. > > phone : 071 7 70 20 50 > mail : [email protected] > > _______________________________________________ > 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 <http://lk.linkedin.com/in/afkhamazeez>* *Lean . Enterprise . Middleware*
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
