Re: Use of Active Directory vs Database (e.g. SQL server)
- From: "Robert Moir" <robspamtrap+msnews@xxxxxxxxx>
- Date: Tue, 4 Oct 2005 13:37:36 +0100
santosh wrote:
> I am designing 2 enterprise applications for my client.
> One of them will be accessed only by internal users, meaning only the
> employees having a valid windows account on the client's domain.
> The other one is however for all the external users. The number for
> users will grow over time and could be over 100,000.
>
> For authentication and authorization purpose, I have recommended use
> of Active Directory. This will obviously work very well for the
> internal application. However, for the external application, I was
> little bit concerned on the scaling of this and was wondering if the
> use of a database will be more appropriate for this. (i.e. whether to
> use active directory or directly use database for authentication).
>
> What are the pros and cons in both of these approaches and which is
> the approriate one for my scenario?
I'd go with Simon's suggestion of ADAM, if the app is a large distributed
one that doesn't natively use its own database server already.
It's worth remembering that Active Directory *is* based on database
technology already, and hence is pretty darn scalable in the right
circumstances.
--
--
Rob Moir
Website - http://www.robertmoir.co.uk
Virtual PC 2004 FAQ - http://www.robertmoir.co.uk/win/VirtualPC2004FAQ.html
Kazaa - Software update services for your Viruses and Spyware.
.
- Prev by Date: Re: Block file copy
- Next by Date: Migrate trusts to child domains
- Previous by thread: Re: Block file copy
- Next by thread: Re: Use of Active Directory vs Database (e.g. SQL server)
- Index(es):
Relevant Pages
|