Hi Jose, On Thu, Feb 23, 2017 at 10:45 PM, JOSE MARIA ALVAREZ FERNANDEZ < josemaria.alvarezfernan...@elcorteingles.es> wrote:
> Hi all, > > As you may know, we are implementing WSO2 in El Corte Ingles, and we are > trying to fit Traffic Manager in our architecture, based on DC/OS and > containers. We would like to know which approach you think it may be better > for the Traffic Manager component. As we are in a PaaS system, we would > like to be able to scale this system out without problems. > > a) It is our understanding that we have to create a different database > schema for every TM instance that we run. We would like to know if it is > possible to run this without having to create a new schema for every > component (that is, share the same schema). If we create a new schema, that > would force us to differentiate the component at DC/OS level, giving them > different configurations for different Traffic Manager instances. > I guess, by scheme you mean database, if so, we don't need seperate database for each Traffic manager nodes. You need to have one database among your Traffic Manager nodes. You can refer Traffic manager deployment patterns here [1] and [2] > > b) If that is not possible, we would like to know if it is possible to run > TM with H2 in memory. As there is nothing that should be persisted in the > TM schema, we thought that could be possible. > We don't encourage H2 database in production. > > If none of the options are viable, what deployment schema would be the > best for this component, taking into account that we would like to be > active/active (being able to scale out)? > Additionally you can refer API Manager clustering guide here [3]. And, common deployement patterns here [4] [1] : http://wso2.com/library/articles/2016/10/article-scalable-traffic-manager-deployment-patterns-for-wso2-api-manager-part-1/ [2] : http://wso2.com/library/articles/2016/10/article-scalable-traffic-manager-deployment-patterns-for-wso2-api-manager-part-2/ [3] : https://docs.wso2.com/display/CLUSTER44x/Clustering+API+Manager+2.0.0 [4] : https://docs.wso2.com/display/CLUSTER44x/API+Manager+Deployment+Patterns > Thank you very much for your help and comments, > > Jose Maria. > > > www.elcorteingles.es > > ------------------------------------------------------------ > ------------------------------------------------------- > > Este mensaje, y en su caso, cualquier fichero anexo al mismo, puede > contener información confidencial, siendo para uso exclusivo del > destinatario, quedando prohibida su divulgación copia o distribución a > terceros sin la autorización expresa del remitente. Si Vd. ha recibido > este mensaje erróneamente, se ruega lo notifique al remitente y > proceda a su borrado. > Gracias por su colaboración. > > This message (including any attachments) may contain confidential > information. It is intended for use by the recipient only. Any > dissemination, copying or distribution to third parties without the > express consent of the sender is strictly prohibited. If you have > received this message in error, please delete it immediately and > notify the sender. > Thank you for your collaboration. > > > _______________________________________________ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Thanks Abimaran Kugathasan Senior Software Engineer - API Technologies Email : abima...@wso2.com Mobile : +94 773922820 <http://stackoverflow.com/users/515034> <http://lk.linkedin.com/in/abimaran> <http://www.lkabimaran.blogspot.com/> <https://github.com/abimarank> <https://twitter.com/abimaran>
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
