Hi,
inline...
Michael Brohl
ecomify GmbH - www.ecomify.de
Am 08.03.22 um 19:11 schrieb Development:
I just don't see the necessity to drop Derby support and exclude those people
who do not want to use Docker (for whatever reason) or need the current OOTB
behaviour.
"need the current OOTB behaviour" is a interesting point. Like even though
ofbiz documentation says to not use derby in production, it's possible that people
actually are. I had not thought of that.
Do we have any way to figure out if people are actually doing that?
The advantage of the embedded Derby is that the database is wiped and
rebuild/loaded with data fast and easy because the database files are
simply deleted and rebuild. No extra dependency on another database,
configuration or external container.
There are several scenarios where it is used, mostly during development
and release management:
- OFBiz standard development (I always develop/test against the latest
code incl. the latest demo data).
- continuous build/tests (buildbot, Jenkins etc.)
- check of the dist files for a new release
(download/unzip/build/testIntegration)
- quick check of the latest trunk/release branch version with the
original load data
- OFBiz demo instances, which are reset every night
- ...
I do not speak about production use and as far as I understand, you were
talking about providing a demo for new users.
So providing a Docker demo might help to get new users started easily.
This can be achieved without changing the OOTB behaviour and dropping
Derby support as proposed.
