为什么 LDAP 没有流行?

发布于 2024-07-14 05:05:31 字数 154 浏览 6 评论 0原文

我们开始使用 LDAP,我想知道为什么 LDAP 没有那么流行? 我读到它的读取速度比数据库更快,但写入速度较慢。

编辑:

这是我第一次使用 LDAP,而且我已经在企业中编程一段时间了。 这就是为什么我认为它不受欢迎的原因,而且我在学校从未听说过它。

We start to use LDAP and I wonder why LDAP is not that popular? I read that it has faster reads than database, however slower writes.

EDIT:

Its the first time i use LDAP and i have been programming in enterprise for sometime now. That is the reason why i thought its not popular, plus i never heard about it at school.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(5

醉生梦死 2024-07-21 05:05:31

我认为 OP 指的是使用 LDAP 类型数据(阅读:分层数据库)作为应用程序数据的存储机制。
虽然很明显大多数网络登录都是基于 LDAP 的,但确实绝大多数业务系统都是基于关系数据模型,很少是基于分层数据模型。

假设这是这里真正的问题:),我将提供一些部分答案,这些答案一起可能完全回答您的问题:

  • 复杂性和高门槛(如 @Elijah 提到)
  • 正如您提到的,学校通常不会教授它 - 因此很多人不熟悉,因此不常用(是这种递归,还是自我实现的预言?)
  • 分层数据模型经过设计优化,可以查找特定数据,并且写入或更新新数据的成本非常高。 最常见的业务应用都是基于OLTP(事务)的,需要大量的写入(BI类应用除外,稍后会涉及到)。
  • 更具体地说,构建分层模型是为了查找数据的特定元素,而不是执行 JOIN、批量选择、GROUP BY 等(我的意思是在逻辑 PoV 中,无论具体上下文如何)。
  • 大多数数据关系型的,或者可以最容易地拟合关系模型。 特别是对于 BI,您希望查看大量数据、执行比较等。
  • 即使对于非关系型数据,我们的思维似乎也被训练认为“关系模型”比分层模型更容易思考(尽管这可能是我的第二点的结果 - 我们大多被教导这一点)。 将数据分类为整齐的行和列只是“更容易”......

I think the OP was referring to the use of LDAP-type data (read: hierarchical databases), as a storage mechanism for application data.
While its quite obvious that most network logons are based on LDAP under the covers, it is true that a huge majority of business systems are based on the relational-data model, and very few are based on a hierarchical-data model.

Assuming this is the real question here :), I would provide a few partial answers, that together probably fully answer your question:

  • Complexity and high bar of entry (as @Elijah mentioned)
  • As you mentioned, it's not usually taught in school - and thus is not familiar to many, and therefore not commonly used (Is this recursion, or self-fulfulling prophecy?)
  • Hierarchical datamodels are by design optimized to find specific data, and very costly to write or update new data. Most common business applications are OLTP (transaction) based, and require a large amount of writes (except BI-type apps, will relate to that in a moment).
  • More specifically, hierarchical models are built to find specific elements of data, and not perform JOINs, mass SELECTs, GROUP BYs etc.(I mean this in a logical PoV, regardless of specific context).
  • Most data IS relational, or can fit a relational model most easily. Especially for BI, where you want to see large swaths of data, perform comparisons, etc.
  • Even for data that is not relational, our minds seem to be trained to think "relational-model" easier than hierarchical (though this might be a result of my second point - we were mostly taught this). It's just "easier" to categorize the data in neat rows and columns...
抹茶夏天i‖ 2024-07-21 05:05:31

您如何得出 LDAP 不流行的结论?
在我工作过的每家大公司中,他们都使用 LDAP 作为访问用户信息中央存储库的方式。

与数据库的比较有点奇怪。 LDAP 是一种协议,而数据库是一个涵盖一大堆产品的术语。 说 LDAP 比数据库更快/更慢就像说 HTTP 比 Web 服务器更快/更慢,特别是因为我希望在每个 LDAP 存储库后面找到某种数据库(甚至可能是关系数据库)。

How do you come to the conclusion that LDAP is not popular?
In every larger company I worked for they used LDAP as a way to access the central repository of user information.

The comparison to databases is a little weird. LDAP is a protocol, while a database is a term covering a whole bunch of products. Stating that LDAP is faster/slower than a database is like saying HTTP is faster/slower than a webserver, especially since I'd expect to find some kind of database (possibly even a relational database) behind every single LDAP repository.

赢得她心 2024-07-21 05:05:31

LDAP 非常流行——它是 Windows Active Directory 使用的协议,(这里是轻描淡写)相当广泛。

LDAP is very popular -- it's the protocol used by Windows Active Directory, which is (an understatement here) fairly widespread.

没有心的人 2024-07-21 05:05:31

LDAP 很棒,它是单点登录和内部工具的绝佳工具。

不确定您所说的比数据库更快的读取是什么意思,它通常从服务器运行,并且通过网络处理身份验证。

它的设计是一个少写多读的系统,但它确实为您提供的不仅仅是数据库中的一个简单的用户表,它还为您处理身份验证,因此您可以将其插入您需要的任何系统。

在工作中,我们将它用于 ssh、NFS、内联网访问、内部工具等等。 如果您使用数据库,则需要在许多不同的系统之间复制身份验证代码。

LDAP is great, its an awesome tool for single sign on and internal tools.

Not sure what you mean about faster reads than a database, it's generally run from a server, and authentication is handled over the wire.

It's by design a write-few read-many system, but it does give you more than just a simple users table in a database, it handles authentication for you, so you can plug it into whatever systems you need.

At work we use it for ssh, NFS, intranet access, internal tools, everything. If you used a DB you would need to replicate the authentication code among lots of different systems.

扶醉桌前 2024-07-21 05:05:31

我认为你说它不受欢迎有点不靠谱。 如果它不受欢迎,你可能不会问这个问题。 然而,我确实认为它的符号和使用有点复杂,并且为相对简单的任务创建了较高的门槛,这可能会影响其采用率。

I think your a little off-base on saying it is not popular. If it wasn't popular you probably wouldn't be asking the question. However, I do think its notation and use is a bit complex and creates a high-bar of entry for a relatively simple task and this may have an effect on its adoption rate.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文