[FINERACT-762] Use of (unmaintained) Drizzle JDBC driver in Fineract at run-time (not build) is sub-optimal for performance

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.4.0
• Labels: scalability technical
• Assignee: Michael Vorburger
• Reporter: Michael Vorburger
• Created: 11/Jun/19 08:41
• Updated: 01/Oct/20 18:37
• Resolved: 17/Apr/20 23:48

Description

Creating this issue to clarify that while FINERACT-761 is focused on (only) the build time use of the Drizzle JDBC driver (which does not lead to it being included in the final Fineract end-user distribution), this is re. the use of it at run-time, which is packaged in the distribution.

The two uses are technically unrelated. While the use of Drizzle instead of Connector/J in the build is a a blocking issue, the use at run-time is not a blocking problem, currently. It's perhaps still not ideal to maintain on a completely unmaintained library (Drizzle) for database access, e.g. for performance.

Issue Links

• blocks: FINERACT-867 Scalability & Performance Enhancements for Supporting Millions of Clients, High TPS, and Concurrent Users
• Dependent: FINERACT-761 Use of (unmaintained) Drizzle JDBC driver in Fineract Build (not run-time) prevents upgrading Flyway <- Gradle
• is blocked by: LEGAL-462 How to use MariaDB (MySQL) in Apache.org (Java) projects, given that the only currently maintained JDBC driver is LGPL?
• is related to: FINERACT-890 Custom slf4j integrated logger for the (optional!) MySQL JDBC driver support in Fineract
• relates to: FINERACT-786 Fineract on Google Cloud ("managed", with Cloud SQL)
• requires: FINERACT-889 Merge (old) DRIVERCLASS_NAME/PROTOCOL/SUB_PROTOCOL) with (new) fineract_tenants_driver/fineract_tenants_url
• links to: GitHub Pull Request #756
• links to: GitHub Pull Request #760