so, I spoke to folds on our slack channel for ActiveMQ. We use for our testsute, and never in production... We can easily replace it by either dockerized databases (e.g Mysql or Oracle), or use HSQL / H2.
We would be happy to use it if there's still a community around it, but if there's not enough community (devs) to keep the project going, we coudln't find anyone at ActiveMQ willing to maintain it. We will just watch this space and decide based on the outcome here. On Wed, Sep 24, 2025 at 5:39 PM Clebert Suconic <[email protected]> wrote: > > from what I spoke to folks on slack channel, Derby is not really > mission critical for us. We could replace by HSQLDB / H2, or just use > a dockerized database. > > > For Artemis this is exactly what I'm planning to do.. use real databases. > > > I will say on the Derby community that we could replace it by > something else if the project goes away. > > On Wed, Sep 24, 2025 at 3:03 PM Clebert Suconic > <[email protected]> wrote: > > > > I saw a discussion today about Derby retiring... > > > > We still use it as part of our testsuites, both on ActiveMQ "Classic" > > and "Artemis"... > > > > > > I wonder what should we do about this? Should we let it retire, should > > we still use it as read-only (as its a good tool for testing), or > > should we ask them to keep it alive? > > > > > > If we let it retire, what would we replace it with? > > > > -- > > Clebert Suconic > > > > -- > Clebert Suconic -- Clebert Suconic --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information, visit: https://activemq.apache.org/contact
