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 <[email protected]> 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
