Hi all,
In my organization we have multiple web apps, each of them serving a different part of the organization.
Because the vision is that all apps will be using the same infrastructure and might share information (pages and services), the original design of the web site was to declare a single web site (single virtual directory), and each of the apps will just be a folder in the site (meaning all apps will use the same iis application).
Of course there is another option in which the infrastructure is built into usable assemblies (cache management, security utils ...) and each of the applications will have it's own virtual directory (and iis application) and will just use the required assembly.
So my question is as follows - has anyone had any experience with the first option has anyone every heard of such a way to implement enterprise web apps can someone direct me to articles on the subject
Much appreciation,
Ido.
Designing web apps in the enterprise
Ramazan Acar
We do it the second way.
It's easier to tune your apps, work with loadbalancing for heavy loaded sites and change the security of a particular site. The first way is easier for the developers the second way is more flexible for the administrator. and he as to work longer with it.
mici
www.dotnetnuke.com
www.rainbowportal.com
Have you looked at them.
jb_cipher
I agree with Clemens,
The second way will also let you do incremental upgrades more easily
if you make a (braking) change in the common infrastructure you don't have to upgrade all the dependend applications at the same time
Arnon
Daya Anand
I agree with Arnon and Clemens. Well, having separate sites for each application will definitely help. It's kinda trade-off which one needs to make. You probably ask following questions to yourself:
1. How many such applications are at the moment and how many it could be in the future
2. How about changes to the applications over a period of time Does a change in one place break another
3. How about security, performance, load balancing and etc matters across enterprise
4. What's the physical location of the servers
5. Does a change in one app need a reboot/restart of the app If yes, in that case, if you dont wanna restart other apps, you will be in prob, so, keep separate.
And many more...
For developers, you can keep common libraries of code and it can be used from within different applications.
Thanks & Regards,
Kans
Anr
What authentication model should be utilized in such environment