• Post Reply Bookmark Topic Watch Topic
  • New Topic

Is it right to keep JNDI in a table

 
Gaurav Chikara
Ranch Hand
Posts: 413
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Is it perfect if we keep JNDI names in a database instead of an LDAP Server
In other words what additional benefits we get if we use LDAP Server for storing of JNDI names
instead of a simple tbale in a database
Anyone Please give your views
 
chanoch wiggers
Author
Ranch Hand
Posts: 245
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
JNDI is optimised for these types of queries (search often update rarely) but there are some differences in performance. Database make some concessions to allow faster updates.
the main reason for using JNDI (from my perspective) is that it is what everyone else is doing so if you access these resources in a database it will be more difficult to maintain.
plus remember that jndi is a hierarchical data source - it is ideal for hierarchical data, while database is a complex relational thing - again, the optimisations that are made are significant under large loads.
finally, companies with existing LDAP solutions will want you to use them to maximise on their ROI and it is sometimes important to seperate configuration details from consumable data.

------------------
Chanoch Wiggers
Architect for Professional Java Mobile Programming
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!