I am considering writing a blog hosting app in ASP.NET MVC. I am new to .NET, but I am quite capable of the lamp world. My question relates to horizontal scaling of user data.
With each blog, every user has something like 6 tables in the database. I want to plan for horizontal scaling so that 20% users can be on a database server, 20% on the other, and so on. . In the lamp world, I will have a "dictionary" table, which I ask for the first time to find out which database the user was on the server. Then the app will only talk to that specific database server.
I do not know how to easily compromise the database used by SQLManshipProvider? Any suggestions?
You can set asp.net subscription to run on a different database from the rest of your place. This will allow you to store all the user information and possibly other related information on a database, while you can distinguish all the information you have in the form of the necessary database.
This subscription will not divide the database, but it will allow you to split the rest of your site into several databases. It is unlikely that the membership database will be a difficult hit by your users anyway.
Comments
Post a Comment