db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrus Adamchik <and...@objectstyle.org>
Subject Re: Embbedded web application
Date Tue, 24 Jan 2006 14:47:41 GMT

Embedded database parent directory is defined by "derby.system.home"  
property. I would usually set it to something known to be writable,  
like System.getProperty("java.io.tempdir").

Can't comment on the performance. Generally I feel like embedded mode  
is not appropriate for a production web application anyways. Somebody  
please correct me if I am wrong, but it seems incompatible with  
clustering for example.


On Jan 24, 2006, at 3:09 AM, sunish kumar wrote:
> Hi,
> Sorry to ask a simple question.
>   Is it okay to use derby as embedded database in my web application?
> In such case where the database files reside? What I am planning is to
> make an application which will just start working with database
> features with out any extra set up. Just copying the war file to
> webapps directory should do everything. It means there may be similar
> applications in the same application server which uses its own
> embedded database. How it will affect the system performance.
> Thank you,
> Sunish

View raw message