Using DotNetNuke for a website like Twitter?

Question

0.00/5 (No votes)

See more:

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?

Posted 9-Dec-10 10:49am

harsimranb

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Mark Vinod Sinnathamby · Answer 1 · 2011-01-10T06:20:00

Hi,
I've worked on a DotNetNuke application that had to be accessed by thousands of people concurrently, and it did not have any issues when i was load testing the portal. But to have a service similar to Twitter running on DotNetNuke, you would have to have a good Hardware infrastructure with fine tuned Databases. DotNetNuke is a CMS system with the ability to create many portals and custom modules with an extendable provider architecture. From one perspective it may be overkill to use it for a service that manages and monitors textual messages from logged on users (you may be able to have a simple and better optimized solution using other technologies). But if you are looking for a extensible site with easy customization and a low learning curve, DotNetNuke might work. It would be best to look at the DotNetNuke case studies out there before coming to any conclusions :)