Traveler can be configured for "enterprise database" (typically, when high-availbility is required).
Currently, the following enterprise database vendor products are supported:
IBM DB2,
MySQL,
Microsoft SQL Server.
See HCL reference: https://help.hcl-software.com/traveler/14.0.0/configurelotusnotestravelerfordb2.html
This idea suggest to add MariaDB to the list of supported databases.
What it means for customers:
MariaDB is particularly interesting on Linux deployments and cloud environments.
Customers can avoid potential issues related to licensing MySQL, as MariaDB is licensed under open source GPL license. MySQL is owned by Oracle.
As a result, Linux distributions (like Red Hat RHEL) prefer MariaDB as default deployment, whereas MySQL needs to be installed from a separate software repository.
MariaDB performs faster than MySQL.
MariaDB has built-in support for HA, i.e. it is easier to build a database cluster.
What it means for HCL:
Wider adoption of the Traveler product, due to to enhanced flexibility.
MariaDB has "limited drop-in" level compatibility with MySQL. Most likely, there is no need to change the Traveler product. It should just work out of the box.
The Traveler documentation would have to be changed to mention support for MariaDB.
HCL Support would need to accept incident cases, where Traveler is configured to use MariaDB (rather than MySQL).
[ Toni Feric, Belsoft Collaboration ]
I would also like to see support for MariaDB. In failover environments, having an active active setup, ensures a much more resilient environment and unlike DB2, doesn't require extra extensive tooling and setup for failover to function. seemlessly.