asp.netsql-serveridentityazure-cosmosdbpolyglot

SQL Server, Cosmos / document DB, Identity membership and polyglot persistence

So here's my situation:

I'm building a web application using .NET Core and React.js. I'm asking what would be the best authentification methods/strategies for my users. In the past, I used Identity in MVC.NET apps to generate Identity table and handle auth and roles, but this time I also want to use a NoSQL database type for hight scalability purpose.

Any thought on the strategy I should use? Is using a polyglot persistence strategy is the way to go? Identity on SQL server and other data on NoSQL?

Solution

  • So I gave it some thought and I think I'll go with Identity as a service, with something la IdentityServer4 or Azure AD for B2C. This clearly divides both concerns in 2 different projects/services. Will see how it goes.