architecture - How to adequately combine a database and an LDAP directory? -

architecture - How to adequately combine a database and an LDAP directory? -

i intend build scheme stores info in relational database (postgresql) , in directory (openldap).

the directory system's users (workers, customers, brokers), each of them has uuid uniquely identifies them; the database things alter (e.g. order details, transactions in progress, etc); some tables in database have uuid attribute, pointing entities in openldap.

a directory chosen because want leverage ability build entities have variable sets of attributes, or entities inherit or combine attributes other classes of entities. such flexibility needed back upwards wider range of business cases.

in other words, directory provides "object-orientedness", have reinvented scratch, had chosen utilize rdbms exclusively.

there's grab not sure how deal yet: if table refers uuid removed directory - database point nothing. info become incomplete or inconsistent.

my solution never remove entities openldap, instead mark them "inactive".

my questions:

is mutual practice utilize directory , relational database in such way? are there other approaches can solve same problem using single component?

database architecture ldap