Dear friends

Help me learn the DNN. I need the feedback for a forthcoming project

1. If I am correct, the DNN framework and its database, will be able to distinguish between the respective data the users belonging to different portals create. Pl. confirm.


2. I would like to create multiple portals. There are 2 options: Either use the child portal (domain.com/portalA) or the parent portal (portalA.domain.com). Which one do you recommend?


3. If we have, let's say, 1000 portals created using this way, will the performance be affected? In my opinion, it should not affect the performance because parent portals and/or child portals are just another way of accessing the underlying logic/data. The performance will coe in picture only if a large number of users access the system simultaneously.

4. Could maintenance be an issue if we make such a large number of portals using the way discussed above? In my opinion, it should not if all the portals can be built and maintained using the same template that comprises the look-and-feel, functionality (modules), roles, etc.

With Regards

1) DNN will maintain distinct data for each portal, however any modules you create wll need to follow the data model to ensure data separation.

2) Selecting parent portal or child portal depends on the project . Typically parent portals are used.

3) As you indicated performance will be based on user access assuming appropriate hardware

4) Maintenance is the main issue with a large number of portals.  If the individual portals are very similar in nature and use only a standard set of modules, then maintenance can be managed.  Any change to the instance will effect all portals, so upgrades need to be planned to keep the interruption to a minimum.   You many wany to consider creating several instances and placing a percentage of portals on each.  All depends on the type of portals being created, host environment, user activity, number of site changes and so on...

Paul.