Apex Code Development You need to sign in to do that
Don't have an account?
Gabriel Argenal Account Skew in Service and Experience Implementation
Hi, I'm relatively new to Experience Cloud. If I anticipate a very large number of portal customers (potentially millions of contacts) will need to get created eventually when users register, what is the best way to avoid account skew? If I configure the experience cloud site in such a way that contacts get created under 1 bucket account, then we will for sure have skew problems right? So how do people typically sol\ve for this? Do they write some apex in the registration handler to create new bucket accounts? or do they do this through batch apex? If anyone can share some insight or post a blog article that would be great.
There's a lot of documentation around skew in salesforce, below are some sources.
Ownership Data Skew: https://developer.salesforce.com/docs/atlas.en-us.draes.meta/draes/draes_group_membership_data_skew.htm
Avoid Account Data Skew: https://developer.salesforce.com/blogs/engineering/2012/04/avoid-account-data-skew-for-peak-performance
Managing Lookup Skew: https://developer.salesforce.com/blogs/engineering/2013/04/managing-lookup-skew-to-avoid-record-lock-exceptions
Trail - Large Data Volumes: https://trailhead.salesforce.com/content/learn/modules/large-data-volumes
https://developer.salesforce.com/blogs/2013/01/reducing-lock-contention-by-avoiding-account-data-skews
If this information helps, please mark the answer as best. Thank you