I noticed this unanswered but closed question (Best Practice for storing User Profile attributes) and am really searching hard for a solution or Auth0 won’t be a suitable alternative to Azure B2C at my organization.
When storing lots of user attributes in Auth0 per the docs (https://auth0.com/docs/user-profile/user-data-storage#example), this incurs a major performance impact. Auth0 doesn’t provide any mechanism to efficiently query user attributes. It’s all-or-nothing.
Does that mean I shouldn’t be storing user attributes of any kind in Auth0 and instead roll my own solution to handle user preferences? Or should I limit those user preferences to very particular pieces of information? If so, what information goes in Auth0? Is there a working example project I can reference for enterprise scaling?
The docs say data should be in an external database only when it’s “data unrelated to user authentication”. If that’s the case, then rolling my own user attributes solution doesn’t match up with Auth0’s documented best-practice.
Based on some logical assumptions, the docs are wrong or don’t fit with any kind of enterprise scaling. The best practice is to always roll your own solution for user preferences unless you either don’t have the resources for custom solutions or don’t care about server load or request latency.
Is there some information someone can provide to clarify or discount my claim?