I was just wondering: what would be the advantages and disadvantages be for DotNetNuke to host a website like Twitter? On the homepage you are showing the newest posts whenever the browser refreshes. You also have thousands of people logging in and out of the website and posting thousands of tweets.

How would DotNetNuke match up to these requirements? Having to access the database so many times in a minute, managing thousands of data in minutes. Would DotNetNuke be capable of such tasks?

My reason to pick DNN was because DNN is already complete.  The need to code many things like User Management, Page Management, Content Management, is already done.  Starting would scratch would only increase the work. 

To be more precise on the question, let me restate it:  Looking at most of the features in Twitter, like User Profiles and User tweeting to other users, do you think DotNetNuke will be able to handle it?  If no, then I do understand that I will have to design my own system where such massive data could be handled.  I do understand that Hosting and SQL Database Size would also play a factor and for that reason I hope to soon start buying my own servers or move to the cloud, but that depends on the requirements.

Also, do you think Windows Server would be a better option for this kind of a website, or Linux.  For Linux, I can't go DNN, but have other alternatives in mind.