ofbiz-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ron Wheeler <rwhee...@artifact-software.com>
Subject Re: Using Derby in Production?
Date Thu, 09 Jul 2015 21:04:08 GMT
Derby is used in production.

http://osdir.com/ml/derby-user-db-apache/2014-01/msg00053.html
http://www.carehart.org/resourcelists/derby_for_cfers/#notdevonly
http://wiki.apache.org/apachecon/Us2005OnlineSessionSlides?action=AttachFile&do=view&target=ApacheCon05usDerbyPerformance.pdf

10 year old comparison of Derby and MySQL
http://wiki.apache.org/db-derby/UsesOfDerby  from the Derby wiki

Testing under your forecasted production transaction load might give you 
a better sense of which database system will give you adequate performance.

Ron


On 09/07/2015 12:09 PM, Pierre Smits wrote:
> Damon,
>
> We advice against the use of Apache Derby as the underlying RDBMS for
> production environments. However, you can read up on how the developers of
> that product think about how to use it at http://db.apache.org/derby/ .
>
> Best regards,
>
> Pierre Smits
>
> *ORRTIZ.COM <http://www.orrtiz.com>*
> Services & Solutions for Cloud-
> Based Manufacturing, Professional
> Services and Retail & Trade
> http://www.orrtiz.com
>
> On Thu, Jul 9, 2015 at 5:47 PM, damon henry <damonhenry@hotmail.com> wrote:
>
>> Is there any rule of thumb or general wisdom about using the Derby
>> database engine in a production deployment?  In previous enterprise systems
>> I have integrated, I have often used Derby during development, but then
>> migrated to a standalone database system before putting things in
>> production.  I am working on my first OFBiz implementation and assumed I
>> would be going that route on this project as well, so tried a few different
>> standalone databases (mysql, postgres, MS SQL Server) with OFBiz, but to be
>> honest I am not seeing any clear advantage, and have in fact run into a few
>> issues with the stand alone databases.  I also work for a much smaller
>> company now than I have in the past.  This is not going to be a large
>> implementation, meaning it is not likely to host lots of simultaneous
>> connections, but once it gets put in place it may be in place for years and
>> accumulate lots of data over the lifetime.  Is Derby up to the task?  Has
>> anyone used Derby over a long period of time and found it to perform well.
>> thanksDamon Henry


-- 
Ron Wheeler
President
Artifact Software Inc
email: rwheeler@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102


Mime
View raw message