Appreciate you shooting that link over and will do some investigation on our end to see what might work best for us.

Thanks!

I have had some discussions on the topic with clients who have a support contract, but it's hard to offer general advice. Generally though, we see folks either push everything into FusionAuth or almost nothing (and just keep an Id referencing FusionAuth in their database). Syncing might work with webhooks. Again, sorry, hard to offer much concrete advice without reviewing your system architecture.

If any community members want to chime in with their experience, that'd be awesome too!

Just wondering if there's any update on supporting an external userstore? We've been running into some complications where it's a bit difficult working with the FusionAuth userstore within our existing application. We have relational data tied to user IDs; however, those users now live within FusionAuth, so we're not able to add foreign key constraints or anything along those lines.

Do you have any architectural best practices or recommendations for handling this? We were thinking of going down the path of potentially syncing the FusionAuth user DB with a DB within our system; however, that could lead to a lot of complexity.

Thanks,
Brennan

We are working on supporting external userstores and it should be available soon.