All geek questions in one place

JNDI: Naming Service and Directory Service

Regarding the Java / JNDI verbiage words, are directory services more complex versions of naming services?

If you read JNDI glossary , it basically defines the following two:

  • naming service - an API that allows you to perform operations in different contexts
  • context - Sounds a lot like a HashMap
  • directory service - an API that allows you to perform operations on directory objects
  • directory object - an object that is in the directory .... (?!?!)

So, if I'm not mistaken, it seems that both types of services allow you to perform CRUD operations for different types of objects, either contexts (in the case of a naming service) or directory objects (in the case of a directory service).

So my question is: what's the difference?!? Are both of these types of context / directory objects really just hashmaps / hashtables under the hood?

I am choking on these differences because I am trying to understand when something is a naming service and when it is a directory service, and these definitions are hard for me to evaluate.

+4
source share
2 answers

Are all of the two types of context / directory hashmaps / hashtables objects under the hood?

No, they are almost certainly database tables under the hood, and they have all kinds of semantics, such as attribute lists, the ability to create child contexts, etc. that hashmaps / hashtables do not have.

+2
source

I think that the directory service is referenced in this acronym only for calling naming conventions with a directory in abbreviation, such as LDAP.

LDAP, DNS, etc. - naming services, because directory services and naming services are synonymous.

From wikipedia :

In software development, a directory is a map between names and values.

Note that on wikipedia, the Name Service is redirected to the same article.

+1
source

Source: https://habr.com/ru/post/1395031/

More articles:


All Articles