Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

When to use LDAP over a database?

Tags:

database

ldap

When should I use LDAP vs. database/key-value-store/column-oriented-database/etc?

like image 450
DavidHH Avatar asked Jul 30 '11 02:07

DavidHH


People also ask

What is the difference between LDAP and database?

LDAP is an application protocol which queries and modifies data by using directory services; a database is a collection of data with on or more uses. 2. LDAP sessions are instigated by clients who connect to the LDAP server; there are various database architectures which many databases use in concert with one another.

When should LDAP be used?

The main benefit of using LDAP is that information for an entire organization can be consolidated into a central repository. For example, rather than managing user lists for each group within an organization, LDAP can be used as a central directory accessible from anywhere on the network.

What is the benefit of using LDAP?

The main benefit of using LDAP is the consolidation of certain types of information within your organization. For example, all of the different lists of users within your organization can be merged into one LDAP directory. This directory can be queried by any LDAP-enabled applications that need this information.

Does LDAP use a database?

The Lightweight Directory Access Protocol, or LDAP for short, is one of the core authentication protocols that was developed for directory services. LDAP historically has been used as a database of information, primarily storing information like: Users. Attributes about those users.


1 Answers

LDAP can be considered a database. But I'm assuming that you mean SQL databases.

LDAP data stores are for systems with high number of reads compared to writes. While other databases such as SQL stores are designed for transactional data usage (high read and writes).

This is why LDAP is a directory protocol. It's well suited to directories where you read lots and write hardly.

From here

LDAP is characterised as a 'write-once-read-many-times' service. That is to say, the type of data that would normally be stored in an LDAP service would not be expected to change on every access. To illustrate: LDAP would NOT be suitable for maintaining banking transaction records since, by their nature, they change on every access (transaction). LDAP would, however, be eminently suitable for maintaining details of the bank branches, hours of opening, employees etc..

And this is another good intro here - LDAP vs RDBMS

like image 82
Preet Sangha Avatar answered Sep 20 '22 18:09

Preet Sangha