If you had to host 500+ DNN portals, how would you do it?
1. Install a single DNN Host installation and create all 500 sites as child portals?
2. Install multiple DNN Host installations, 1 for each portal?
3. Install multiple DNN Host installations, with 10-50 child portals per host installation?
considering the following requirements...
1. Each portal had between 10 and 20 pages.
2. Each portal had between 25 and 50 users.
3. Each portal had between 200 and 500 unique visitors per day requesting approx 50 pages per visit.
4. Each portal site contained modules that accessed a database that was not the DNN host database.
5. The User and Role information for each portal site was also used for authentication to separate 3rd party applicaitons.
(any suggestions how to do #5 would be a godsend (without use of Active Directory, portal admins have to be able to add/remove users))
Optional
1. Portal administrators would like the abiliity to request that 3rd party modules be installed for use in their portal.
Very Optional
2. Modificaiton of the DNN file and folder naming scheme to support key words for high organic search engine placement.
Concerns
Single DNN Host with 500 child portals
1. Single Application pool for 500 sites with heavy 3rd party applicaiton use.
2. Troubleshooting bugs without option to delete and re-install
3. Domino failure of child portals
4. Security of 3rd party module installation and client data.
500 Separate DNN Host Installations
1. Portal management, module installations and bug fixes of 3rd party apps across 500 separate DNN installations
2. Authentication and User/Role connection complexity between DNN database and 3rd party applicaitons with multiple stand alone DNN host installations.
3. Data storage requriements with 500 individual DNN host installations versus a single Host with 500 child portals.
I can't begin development until I answer these questions.