[directory-site] branch production-readiness created (now f6859a0)

[se...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

seelmann pushed a change to branch production-readiness
in repository https://gitbox.apache.org/repos/asf/directory-site.git.


      at f6859a0  Add production readiness statement

This branch includes the following new commits:

     new f6859a0  Add production readiness statement

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.

[directory-site] 01/01: Add production readiness statement

[se...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

seelmann pushed a commit to branch production-readiness
in repository https://gitbox.apache.org/repos/asf/directory-site.git

commit f6859a09a1ea87e21b5a8223226df753190196f2
Author: Stefan Seelmann <ma...@stefan-seelmann.de>
AuthorDate: Fri Apr 9 19:56:11 2021 +0200

    Add production readiness statement
---
 layouts/apacheds/baseof.html            |  1 +
 source/apacheds/production-readiness.md | 25 +++++++++++++++++++++++++
 2 files changed, 26 insertions(+)

diff --git a/layouts/apacheds/baseof.html b/layouts/apacheds/baseof.html
index 936889e..5c4476c 100644
--- a/layouts/apacheds/baseof.html
+++ b/layouts/apacheds/baseof.html
@@ -36,6 +36,7 @@
                     <li><a href="/apacheds/">Home</a></li>
                     <li><a href="/apacheds/news.html">News</a></li>
                     <li><a href="/apacheds/features.html">Features</a></li>
+                    <li><a href="/apacheds/production-readiness.html">Production Readiness</a></li>
                 </ul>
 
                 <h5>Downloads</h5>
diff --git a/source/apacheds/production-readiness.md b/source/apacheds/production-readiness.md
new file mode 100644
index 0000000..13996f4
--- /dev/null
+++ b/source/apacheds/production-readiness.md
@@ -0,0 +1,25 @@
+---
+title: Production Readiness
+---
+
+# Production Readiness
+
+Due to some critical issues related to data corruption, we are not considering Apache Directory Server to be production ready. This is a well known issue, which is quite complicated to fix. We had added some repair command to work around the problem, but this is is just a workaround, and we know it won't fix all the data corruptions.
+
+Would you decide to use Apache Directory Server in production, we would strongly suggest two things:
+- first avoid updates as much as possible. If you load data once, and use the server in read only mode, you should be safe
+- otherwise, be sure to have backups. This is the only safe way to get back to your feet if you have a serious data corruption that can't be solved by the 'repair' command.
+
+The same kin of problem has hit OpenLDAP a while back, when they were using BDB as their default database. The smart move they did was to develop LMDB which is not only superior in all aspects, but also is guaranteed to be bullet proof by design against data corruption.
+
+We have started moving in the exact same direction with Apache Mavibot, but the work is not completed yet (although we could have a version that works with Mavibot soon enough, but without dead data removal).
+
+Long story short, we are working on solving this issue, it's complicated, it's time consuming, and it will take a while.
+
+OTOH, Apache Directory Server was designed from day one to be almost fully compatible with OpenLDAP. That means you can develop and test your solution using Apache Directory Server, and move the schema and data to OpenDLAP once ready, on your production server.
+
+We believe Apache Directory server still is bringing great value for testing purposes, development and education, until we fix this data corruption issue.
+
+Also keep in mind this is all a volunteered effort, and we only can do as much as we can. More volunteers would help, of course.
+
+In the mean time, we thank you for your support - and bugs reports -, this is quite an adventure to work on such a 500 000+ SLOC code base.