How are Social Networks made? ASP.Net Create for each User a Static page /myname.aspx how does it work?

Question

User-1429135670 posted

How are Social Networks made? The user and link architecture e.g for each user a page is created? 

I'm Franz [15 years old], I've discovered that myspace is built in asp.net. I will like to make my own social network that people can chat anonymously and people can like, follow etc. But my problem is how static pages for users are Created? 

For Example, Facebook, if a user creates Account he gets a static URL: facebook.com/myusername..... Please, how can I do so in ASP.Net? If it is: mywebsite.com/account I can do so but I may like to do so!

Thanks very much! 

Answer 1

User753101303 posted

Hi,

You'll need to learn a lot and maybe you'll do much other things first, but the basic idea regardless of the exact technology is that the incoming url is processed on the server to be directed to the corresponding resource.

So if you are using site.com/user/patricesc or site.com/user/franz the web server will see first if it finds this physical file or folder on the server. if not it will try to find if something handles all site.com/user/<whatever> requests which will be usually some code.

This code will then grab the <whatever> value to retrieve data from a database and renders a web page all along with those information to show the matching information. As a result you are able to see data for any user using just a single page (rather than creating a separate static page for each user).

Answer 2

User541108374 posted

Hi,

you can make use of routing in both webforms and MVC to accomplish this. Make a route for /{nameofuser} and have the view generated filled with the information you need.

For social networks and the high volume they generate companies tend to make use of caching a lot and graph databases to speed up performance, generating less html and more spa like applications with web api's in the backend.

Depending on how your social network will grow over time you'll likely find yourself upgrading and rewriting your code and tossing database flavor A for flavor B for your specific needs so be prepared to be very agile.

Personally I would start with a cloud serverless approach (Azure) and use Redis cache, API gateway, and depending on what I need CosmosDB or SQL DB in combination with storage and service bus/queues for throttling the input of the users. Then optimize on use later on and have clean devops story ready for fast rollouts.

Kris.