Geek asks and answers

LDAP vs Relational Database

I come to you after a desperate disappointing Internet search to answer my question: Which one is faster: LDAP or a relational database?

I need to configure a system with user authentication and authorization. I know that LDAP has a “structure” for this kind of need, but is it really faster than, say, MySQL?

+5
source share
3 answers

For authentication and authorization purposes, in my opinion, LDAP provides the best combination of performance and simplicity, as well as installation and maintenance. LDAP as a protocol is quite small, requiring relatively little network bandwidth. A small protocol also makes encrypted transmission quite high.

LDAP is also simple, servers are easy to deploy, and state-of-the-art professional-grade LDAP servers provide impressive performance over a relational database, all other things being equal, such as hardware and query type.

, , , , LDAP - . , LDAP, , 28 000 postgres, 42% , .

LDAP , -, AES, , SASL DIGEST-MD5 .

+7

, , . . , , , LDAP .:) ...

, , , , . MySQL/MSFT SQL Server/ .. , () . , QP, . LDAP, , -... , ( RFC RFAP). AD, , ... . (, auth).

, , .

, , .

+5

IMO, this is not a question, because it always depends on specific implementations .

I can only add my experience: LDAP is slow, SQL is fast. I use MS SQL 2008, and in my case it is very fast thanks to the intelligent caching of repeated queries.

But do you need to be exceptionally fast? An LDAP-based solution can often offer easier and better integration with other software and / or LAN infrastructure when dealing with users, authorization, and authentication.

0
source

More articles:


All Articles