Hi Isuru, To me the main reason is the improved security in having these separate. A potential breach into either will not impact the other.
The next reason is also related to security but also simplifies management (i.e. replication, back-up-and-restore etc.) as well. That is when you federate the registry or the user permission store - they might be done in different ways. Having these two separate databases makes it easier to share only what you want, instead of making everything available always. Given the good habit of not overloading a single server, a shared connection pool wouldn't harm most standalone production deployments, but if you have multiple tenants etc, its is good practice to separate these as Amila pointed out. Because the access patterns of the registry and UM are not the same, having separate pools improves performance. Thanks, Senaka. On Mon, Dec 23, 2013 at 10:53 AM, Amila Maha Arachchi <[email protected]>wrote: > Hi Isuru, > > Several reasons which I can think of. > > 1. Same DB Connection pool will be used if you go with single database. > This can affect userstore operations or registry operations if the load to > one becomes high (say the registry invocations increases, userstore > operations might get affected). > > 2. There's also a good practice to create two separate DB users (userstore > user and registry user) and grant permission for them to only access the > necessary database. This is good for security as well. > > 3. It is nice to separate these two :). Ideally what I do is, create two > databases. When doing this, I get the original script and remove the > unwanted tables and create two separate scripts (registry.sql and > userstore.sql) > > Regards, > AmilaM. > > > On Sun, Dec 22, 2013 at 3:35 AM, Isuru Perera <[email protected]> wrote: > >> Hi, >> >> $subject? >> >> It's mentioned in docs [1]. >> >> I believe we can use the same database. We also use the same script to >> create databases for Registry and User Manager. >> >> I would like to know the reasons? >> >> Thanks! >> >> Best Regards, >> >> [1] http://docs.wso2.org/pages/viewpage.action?pageId=29918203 >> >> -- >> Isuru Perera >> Senior Software Engineer | WSO2, Inc. | http://wso2.com/ >> Lean . Enterprise . Middleware >> >> about.me/chrishantha >> >> _______________________________________________ >> Dev mailing list >> [email protected] >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > *Amila Maharachchi* > Senior Technical Lead > WSO2, Inc.; http://wso2.com > > Blog: http://maharachchi.blogspot.com > Mobile: +94719371446 > > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- * <http://us13.wso2con.com/> * *Senaka Fernando* Senior Technical Lead; WSO2 Inc.; http://wso2.com * Member; Apache Software Foundation; http://apache.org <http://apache.org>E-mail: senaka AT wso2.com <http://wso2.com>**P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://linkedin.com/in/senakafernando <http://linkedin.com/in/senakafernando>*Lean . Enterprise . Middleware
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
