up vote 1 down vote favorite
share [g+] share [fb]

What are the pros and cons of running an ASP.NET web application in a domain (having domain controllers etc)

Edit Is it possible to scale up to a Server Farm without a domain? yes

Pros:

1) Easier to Manage Permissions/Access across machines?

Cons:

1) Requires additional machines/expertise (domain controller and possibly a backup)

(will update based on answers)

link|improve this question
belongs to serverfault.com/ maybe? – 0xFF Aug 21 '09 at 10:45
I did think that, but its more of a configuration thing that a "fault" or is serverfault for servers and superusers for desktops? – Mark Redman Aug 21 '09 at 11:00
Belongs definitely on Server Fault. Server Fault is not only for "faults". ;) It's for server-related questions in general. – Albic Aug 21 '09 at 11:11
Hi, ok great..new to SF and SU...I see its been moved! – Mark Redman Aug 21 '09 at 11:33
feedback

migrated from superuser.com Aug 21 '09 at 11:24

This question came from our site for computer enthusiasts and power users.

1 Answer

up vote 1 down vote accepted

You don't need to run a domain to do a farm but I guess it will simplify your set-up a little in respect of permissions etc as you've said. You'll still need to do the usual MachineKeys syncing etc between servers to handle scenarios where requests are jumping between servers.

It's generally not recommended by MS to have your public facing web (or DB servers) also acting as DC's although I've done it on a number of occasions where we had limited resources and never had any issues.

link|improve this answer
feedback

Your Answer

 
or
required, but never shown
discard

Not the answer you're looking for? Browse other questions tagged or ask your own question.