So your primary complaint with 389 is that it's built on a BerkleyDB backend? At the very least, there is some technical merit to this position and it looks lik

So your primary complaint with 389 is that it's built on a BerkleyDB backend? At the very least, there is some technical merit to this position and it looks like Red Hat is currently working on getting 389 to work with other databases; they mention LMDB as a specific example. https://directory.fedoraproject.org/docs/389ds/design/backend-redesign.html https://directory.fedoraproject.org/docs/389ds/design/backen...