AEM support for 1000+ jcr nodes - user profile/products | Community
Skip to main content
varshsr
varshsr
Level 5
October 16, 2015
Solved

AEM support for 1000+ jcr nodes - user profile/products

  • October 16, 2015
  • 13 replies
  • 6688 views

Please share your thoughts on these questions

1) I see recommendation on JCR content models to keep child nodes limited under 1000 nodes . Is the same applicable for JCR user profile nodes as well  ? if there is a need to support an public site which can have 300K end users ? Does AEM support 300K JCR user nodes (keeping 1000+ jcr node limit and better performance) assuming all these users are provisioned either all at once (old users) or created after custom authentication  (new users) ?

2) Also can we assume this limitation (JCR 1000 + node) is irrespective of TarMK or MongoMk storage considering limitation is on JCR API based content access which is common for both TarMK or MongoMK ?

3) Also if we need to use Personalization / AEM Communities with end user ACL , assuming that these user profiles needs to be reverse replicated to author and synchronized across publish clusters. Is there any possible / known risks in maintaining end user profiles in AEM ?

4) If there is a limitation please let know what is the maximum / possible user profile nodes /content (product) nodes support in AEM with CRX2/CRX3 - OAK Repository ?

3) In case we need to support e-commerce portal what is the limitation on product nodes and possible risks assuming author syncs with a PIM to import / create product nodes which can be more than 150 K ?

4) Even if assume that Product and UGC can be bucketed based on some time stamp ? How to decide on 300k user profile nodes which might have different possibilities and might not fit into a particular pattern buckets?

5) Overall looking for some best practices on end user profile nodes and product data nodes within in AEM ?

 
    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by joerghoh

    Please consider, that these numbers are ok with the repository itself. But when you have 300k+ users, you need to have the right user interface to manage these massive numbers. And that's a case, for which the AEM /useradmin isn't really designed for.

    Jörg

    13 replies

    Show previous replies
    BSetty
    BSetty
    October 17, 2016

    Good points Opkar. What kind of site is this?  This is exact questions that pop in mind when we hear requests from clients / biz.

    As Architects/consultants, we always come across question on not using AEM user repositories. Doesn't AEM support user sessions, user management, access permissions, personalization; SAML/OAuth based login handling? YES AEM supports everything mentioned above. In fact for SAML/OAuth based login, user need to be present in Oak core. Core personalization depends on persisted users in repository.  Also, these featurs can be realized using social communities. May be we can tweak platform to pull those features out of social communities but none the less its customization. 

    In my mind, AEM is a great WCM and part of greater marketing cloud. But certainly they are not on par with application servers like oracle/JBoss. CRX - TarMK doesn't replace oracle database (RDBMS)/ mongo DB. Though it can play role of service provider in SSO solution using SAML Auth Handler, it can't replace as complete SSO Solutions like IBM/Site Minders of world. They don't really replace ESB for service orchestration. Every engagement starts with demystifying above points and sometimes to an extent of proving points.

    Some of demerits that are evident if we choose to manage users in AEM and should be highlighted are

    1. Session management across multiple publish nodes

    2. User synchronization across multiple repositories

    3. Integrating user repositories to DMP for constantly evolving segments (audience manager)

    4. Integrating user repositories to Target / Campaign mgmt for personalization

    There is no one article on managing users from house of Adobe and recommended practice. I see there are Architects from Adobe who can consolidate recommendations.

    BSetty
    BSetty
    October 17, 2016

    Good points Opkar. What kind of site is this?  This is exact questions that pop in mind when we hear requests from clients / biz.

    As Architects/consultants, we always come across question on not using AEM user repositories. Doesn't AEM support user sessions, user management, access permissions, personalization; SAML/OAuth based login handling? YES AEM supports everything mentioned above. In fact for SAML/OAuth based login, user need to be present in Oak core. Core personalization depends on persisted users in repository.  Also, these featurs can be realized using social communities. May be we can tweak platform to pull those features out of social communities but none the less its customization. 

    In my mind, AEM is a great WCM and part of greater marketing cloud. But certainly they are not on par with application servers like oracle/JBoss. CRX - TarMK doesn't replace oracle database (RDBMS)/ mongo DB. Though it can play role of service provider in SSO solution using SAML Auth Handler, it can't replace as complete SSO Solutions like IBM/Site Minders of world. They don't really replace ESB for service orchestration. Every engagement starts with demystifying above points and sometimes to an extent of proving points.

    Some of demerits that are evident if we choose to manage users in AEM and should be highlighted are

    1. Session management across multiple publish nodes

    2. User synchronization across multiple repositories

    3. Integrating user repositories to DMP for constantly evolving segments (audience manager)

    4. Integrating user repositories to Target / Campaign mgmt for personalization

    There is no one article on managing users from house of Adobe and recommended practice. I see there are Architects from Adobe who can consolidate recommendations.

    Gdubz-57m2mu
    Gdubz-57m2mu
    Level 5
    October 19, 2016

    Opkar Gill wrote...

    Reverse replication for users has been deprecated and you should use SCD to sync users across a TarMK farm.

     

    @Opkar Gill - I took a look at the documentation for User Sync with SCD. How is this different than Forward Replication/Reverse Replication? It doesn't use Replication Agents, so I'm guessing it's closer to the Sling layer and takes fewer resources to process maybe?

    Flow-wise it sounds exactly the same, just done through OSGi console configs instead of an admin/authoring interface. It's still using the Author instance (and it's resources that are already being shared with the currently active authors) as the arbiter to distribute content between a horizontally scaled publish farm.

    This line in the above documentation kinda scares me away from even trying to use UserSync/SCD:

    "With infrequent updates, it is reasonable for user data to be synchronized with other publish instances using Sling Content Distribution (Sling distribution)."

    I say that mostly because right now we've got some custom FR/RR agents working to keep 4 publish instances in sync, with 10k+ active users. Trying to keep profile preferences and things in sync is basically killing our single author instance right now, making the content authoring experience horrible. I really hope SCD is a better solution. :(

    Terms & ConditionsAccessibility statement

    Loading footer...