Background - I understand so far - Since all the membership data will be in the same division, this may be the reason for the table for a long time.
Currently, I only register the user in my system based on e-mail and password. I also have a user table on the Azure SQL, and I have the obligation between the two at the application level. The "foreign key" is the e-mail address.
URIID / Key is not emailed for the search of users using a subscription provider
Next to the homepage, it is necessary to certify another site, so I hope the use of membership will be important, but not too big, because after the authentication the user is cached for a few minutes. / P>
Do you think membership-based table-storage is usually a good practice for millions of users? What specific issues would you recommend to me? Subscription provider is a 2005.net 2 residue that should be kept out of their misery There is no room in modern web architecture The application should work with claim-based authentication and offload the identity in the service which is more capable. If you are serious about being able to scale millions of users, then you feel that really tough about identity ??? Because it is important to use a membership provider, you can paint in the corner of an architecture that is at odds with your ambitions.
No comments:
Post a Comment