I'm creating a type of social networking site.

I have to choose which platform (ASP.Internet MVC, PHP, Ruby…).

I'm also thinking about using out-of-the-box solutions as DotNetNuke, Drupal, Joomla and so forth.

My natural drive was to choose ASP.Internet MVC 3 (with Razor view engine), since i have am experienced .Internet developer (not web) also it appears just like a fun to understand.

But, I suppose you will find out-of-the-box solutions which will most likely shorten the expansion time considerably.

Obviously there's dependent on speed versus acquired experience and fun (which I have to determine with myself).

I'll be thrilled to have any suggestions about the problem.



While you describe under consideration that you're curently have experience of .internet that ASP.Internet MVC is the best for you.

ASP.Internet is a superb but it is insufficient to make an internet site so other factor you'll need that

jQuery for javascript development [opensource] MySQL for Database management [opensource]

You will find some missing informations on which exactly you are attempting to achieve.

A social networking website is a nice large subject. Inside your question you didn't remember to say in which you were likely to store your datas. What platform will you use for server.

Could it be a Unix(linux, bsd, macos, solaris...) server or perhaps a Home windows server.

You could utilize a SQL database or perhaps a NoSQL database for datas. Just in case of internet sites it will work better to utilize a NoSQL database (document oriented database).

For the word what, you need to pick one that matches you well but additionally works best for your database.

Complete solutions

As I'm not sure what you are striving for, you will find chances that you could match such things as drupal. You'd have to ascertain if all of the modules you'll need exist. Then you'd need to define a style as needed. But to tell the truth after experimenting with drupal. I'd state that if you want to do anything whatsoever that needs plenty of modules. It may be a much better idea to construct something because of your own utilizing a framework.


What's right with frameworks is the fact that they are frequently fairly simple and allow you to focus on the key stuff without replacing from crash. For exemple, Used to do websites in python while using pylon frameworks. Things I loved relating to this framework is it does not enforce anything. You should use different database, different template engine if any. All of the framework does is handling demands and redirecting them right controller.

What's great about frameworks is they allow you to do complex items that complete solutions can't do effortlessly. But however you are able to mess everything up if you are not careful.

Here's a listing of stuff you should take a look at:

SQL databases: Mysql, Postgresql

NoSQL databases: MongoDB, CouchDB

Python frameworks: Pylons, TurboGears2, Tornado, Flask

Ruby frameworks: Rails

PHP frameworks: Symfony, CakePHP

I am likely to show you Drupal Commons by Acquia, it is a distribution of Drupal 6 that's an as they are social collaboration tool. It might be a terrific way to evaluate Drupal's versatility/abilities/contrib-modules for the reasons (that are slightly vague right now):