I am planning to build a communication system based on mongooseim platform. I still want to use common user group across all the applications. What is the best stratergy of avoiding data duplication and maintaining rosters backend outside the mongooseim database structure.
Currently MongooseIM supports 3 backend types to store roster:
If you want to integrate roster with your other web service without data duplication, you need to implement new backed talking to your service directly.
A generic backend is a good idea, I'll discuss this with the team and probably we add it to our backlog. I'm not able to promise any dates when this would be implemented, though.