From: Krzysztof B. <kb...@un...> - 2018-03-13 15:04:12
|
Hi, W dniu 13.03.2018 o 11:48, Sami via Unity-idm-discuss pisze: > Hi, > > Couple of years ago the documents describes primary/local databases > and it was possible to share same primary database instance between > multiple unity-idm instances. > > Current documents from decent versions doesn't anymore describe local > and primary databases, so I assume that there is just one. So the > question is, can that database be shared between multiple unity-idm > nodes which are running simultaneously? Yes. The Unity 1.x so called DB was dropped. If you share the only remaining main DB between multiple instances this should work. The safest bet is to also pin HTTP sessions to the same instance on the balancer/router. We use it for master/slave(s) redundancy setup, not for performance scaling. > I understand that Hazelcast at least comes to this scenario where all > hosts in the cluster shares same in-memory database which is synched > to this "one/shared" database instance. > What is the status of Hazelcast, it seems to be still experimental but > is there any estimates when it achieves the maturity to be stable for > production use? Well, this should work quite well, all our tests on Hazelcast work fine, we are not aware of any problems. Although up to my knowledge this was not used in production anywhere and all the tests where run on Hazelcast cluster with certain - simple - configuration. We don't have very concrete short term plans to work on this more (basically creating deployments and testing), rather waiting for community feedback. This is on our long term plans for providing Unity SaaS offering. Cheers, Krzysztof |