SOLVED
Maximum allowed users in publish
1 Accepted Solution
Correct answer by
@vb11 The biggest issue we faced with authenticated users are stored in JCR is "syncing user and group" issues between publish instance. We felt SCD(Sling Content Distribution) which sync the user profile updates or new user node generated in one of the publish instance to other publish instances through Author is buggy. The distribution queue got stuck and filled with unfinished jobs in Author. So you will end up seeing new user's post in community forum coming as "Unknown" user in other publish instances since that publish instance didn't get synced with this new user. We have around 400K users(B2B). SCD set up is cumbersome and painful to troubleshoot every time we hit the user related issues.
On the side note, its interesting to see client moving to AEM communities now considering Adobe is not planning to upgrade AEM communities or put more effort to improve. Just the support. So we moved out of AEM communities for the same reason.
Having Mongo as SRP will be good and hope you can have control and admin privilege for this to see how the UGC are stored and troubleshoot. We had ASRP and it was total black box , you can only use SRP browser and it was buggy too.
Those are my inputs, hope it helps.
Hi @vb11 ,
There are some best practices and recommendations to consider:
1.Since you already have a large user database, it's important to plan and execute the user migration process carefully. You can leverage AEM's user synchronization capabilities or develop a custom solution to import the users into AEM's JCR repository. Ensure that user attributes and authentication mechanisms are properly mapped and integrated with the third-party authentication provider (AWS Cognito).
2. With a large user base, it's crucial to design your AEM infrastructure for scalability and performance. Consider using a distributed setup, load balancing, and proper caching mechanisms to handle the increased load. Optimize your AEM instance configuration and monitor system resources to ensure smooth performance.
3. Assess the user groups and roles in your existing community site and map them to AEM's user groups and permission models. Define appropriate access controls and permissions to manage user access and content moderation within the AEM Communities environment.
4. As you mentioned, storing user-generated content (UGC) externally on a separate database (e.g., MongoDB or MySQL) is a recommended approach. This helps in offloading the storage requirements from the JCR repository and improves performance and scalability.
5. Ensure seamless integration between AEM and AWS Cognito for authentication. Implement proper user synchronization and session management to maintain user authentication and authorization across the platforms.
It's also advisable to engage with Adobe Support or Consulting Services to discuss your specific requirements, perform a thorough architecture review, and get guidance on any potential known issues or specific recommendations for your migration scenario. They can provide further insights based on their expertise and experience with similar implementations.
Correct answer by
@vb11 The biggest issue we faced with authenticated users are stored in JCR is "syncing user and group" issues between publish instance. We felt SCD(Sling Content Distribution) which sync the user profile updates or new user node generated in one of the publish instance to other publish instances through Author is buggy. The distribution queue got stuck and filled with unfinished jobs in Author. So you will end up seeing new user's post in community forum coming as "Unknown" user in other publish instances since that publish instance didn't get synced with this new user. We have around 400K users(B2B). SCD set up is cumbersome and painful to troubleshoot every time we hit the user related issues.
On the side note, its interesting to see client moving to AEM communities now considering Adobe is not planning to upgrade AEM communities or put more effort to improve. Just the support. So we moved out of AEM communities for the same reason.
Having Mongo as SRP will be good and hope you can have control and admin privilege for this to see how the UGC are stored and troubleshoot. We had ASRP and it was total black box , you can only use SRP browser and it was buggy too.
Those are my inputs, hope it helps.
