> On Jul 14, 2023, at 12:32 AM, Emmanuel Lécharny <[email protected]> wrote:
>
> A bit of history:
>
> ApacheDS was started in 2002 by Alex Karasulu, who brought is own effort
> (Ldapd) into the Apache incubator in october 2003, so pretty much 2 years
> *before* Neil Wilson started to work on OpenDS.
> We offered the OpenDS team to coodinate our efforts when we announced
> ApacheDS 1.0 in 2006 at Austin, during the ApacheCon conference. This never
> actually happened, as Sun was already fighting with internal difficulties,
> leading to the departure of Neil and a few collegues to create UnboundID.
> We tried to start a common effort to design what is now the LDAP API with
> Sun, and it somehow leads to some work been done in common, but at the end,
> Sun completely let down.
>
> I don't see the point in forking OpenDS; it's already 17 years old, and would
> require a huge effort to get to live. Plus who will engage in thsi effort?
>
> All in all, I'm not sure OpenDJ or OpenDS has made a lot of impact on the
> industry, which is currently dominated by Active Directory (for the worse)
> and OpenLDAP.
>
Time flies. I remember, circa 2000, when Sun dominated the directory space and
OpenLDAP was the “toy”.
Back then M$ couldn’t even spell LDAP ;-)
Things have changed. I pretty much agree with your characterization of how
things stand.
Where there might be a difference is ApacheDS should be usable in prod.
Small to medium sized prod installations.
—
Shawn
> So we still think there is some space for ApacheDS, but in a different area.
> We decided from day one that ApacheDS should be as compatible as possible
> with OpenLDAP, because we guys are working i the same spirit of true Open
> Source. And actually, migrating from ApacheDS to OpenLDAP should be a breeze.
>
> Our main pros are that you can use ApacheDS as a test bed while developping
> your Java application based on a OpenLDAP server without having to deal with
> teh complkexity of installing and managing OpenLDAP during the development
> phase: you can embed ApacheDS as a test environment
> (https://directory.apache.org/conference-materials.data/testing-LDAP.pdf)
> without having to deal with cleaning up anything in between tests, à la
> testContainer but without the extra 10 seconds required to start the
> container...
>
> Plus we have Studio, which is extra util.
>
> Bottom line, we have a path to get ApacheDS being production ready, it's now
> just a matter of time to get it on track.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
