We are looking to use crowd as the central ID server. The one obvious thing about such a system is that it must be resilient. We are mostly cloud based (Digital Ocean) & as such can have many instances or possible instances of crowd.
So .. what is the best way to guard against machine/OS/app failure ?
Postgres replicating out?
Doing a nightly xml dump & importing it into clone crowd instances?
e.g. in essence if "crowd1" goes down for whatever reason we'd rather people/users didn't even know & as such "crowd2" takes over etc.
Has anyone done a multi-instance crowd setup with fault tolerance as a key goal?
There's a similar topic on this question where you also can find some ideias as well:
Also, there is this improvement request which I suggest you to vote:
To sum up, if you haven't already, we recommend you check out Go2Group's white paper on a clustering solution:http://www.go2group.com/en/services/atlassian-services/atlassian-crowd-a-simple-clustering-solution/. Whilst running Crowd in a cluster is unsupported, this may help some of you, although be aware that there are known unresolved configuration issues: https://jira.atlassian.com/browse/CWD-2925
I'm John Allspaw, co-founder of Adaptive Capacity Labs, where we help teams use their incidents to learn and improve. We bring research-driven methods and approaches to drive effective inciden...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs