I am wrestling with the idea of storing our entire application directly in
the database. I am looking for a little advice ( Pros/Cons ) from anyone who
has tried this before.
Jorsek Software LLC.
"CaseyDJordan" on LinkedIn, Twitter & Facebook
Cell (585) 771 0189
Office (585) 239 6060
This message is intended only for the use of the Addressee(s) and may
contain information that is privileged, confidential, and/or exempt from
disclosure under applicable law. If you are not the intended recipient,
please be advised that any disclosure copying, distribution, or use of
the information contained herein is prohibited. If you have received
this communication in error, please destroy all copies of the message,
whether in electronic or hard copy format, as well as attachments, and
immediately contact the sender by replying to this e-mail or by phone.
From: Wolfgang Meier <wolfgang@ex...> - 2009-12-24 09:44:58
> I am wrestling with the idea of storing our entire application directly in
> the database. I am looking for a little advice ( Pros/Cons ) from anyone who
> has tried this before.
One advantage is that you can backup your entire application as one
package. Migrating to a different machine will be easy as it just
means restoring a backup. eXist will transparently store all binary
resources on the file system, so performance wise, there should not be
much of a difference.
Keeping the app in the file system has the main advantage that you can
directly use SVN on it. If the app resides in the db, you would need
to first backup to the file system to commit to SVN (Dmitriy is
working to support SVN on db collections though).
The 1.4 release also allows a mixture of both approaches. You can
configure multiple web app roots via controller-config.xml in