Java Naming and Directory Interface (JNDI)

Key facts

First appeared

1997

Category

technology

Problem solved

JNDI was created to solve the problem of fragmented and inconsistent access to diverse naming and directory services in enterprise computing. Before JNDI, Java applications had to use different, proprietary APIs to interact with services like LDAP, DNS, or CORBA Naming Service, leading to complex, non-portable, and tightly coupled codebases. JNDI provided a single, abstract API to access these disparate services uniformly.

Platforms

Any platform running a Java Virtual Machine (JVM)

Related technologies

• LDAP (Lightweight Directory Access Protocol)
• Application Servers (e.g., Apache Tomcat, JBoss/WildFly, WebLogic, WebSphere)
• JDBC (for data source lookup)
• DNS (Domain Name System)
• RMI (Remote Method Invocation)
• Java Message Service (JMS)
• Enterprise JavaBeans (EJB)
• Java EE (now Jakarta EE)

Notable users

• All enterprises utilizing Java EE/Jakarta EE application servers
• Companies with large Java-based backend systems
• Organizations relying on LDAP-based authentication/authorization in Java applications