You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@fineract.apache.org by "James Dailey (JIRA)" <ji...@apache.org> on 2018/10/04 22:16:00 UTC

[jira] [Commented] (FINCN-26) Replace MariaDB driver with drizzle as JDBC driver

    [ https://issues.apache.org/jira/browse/FINCN-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16638958#comment-16638958 ] 

James Dailey commented on FINCN-26:
-----------------------------------

A little research on this seemed in order, and this blog entry on performance is as good a place as any to start:  [https://mariadb.org/on-performance-of-jdbc-drivers/]  

This is from a 2013 benchmark of Maria, ConnectorJ, and Drizzle Connectors.  The preference on a Maria site is clearly Maria, but if that is eliminated, then Drizzle rises to top on the basis of performance after a bug was found and corrected.  Which points to two other elements of this decision:  how stable are these connectors and will support be available longer term?  Also, are there any other type 4 ODBC drivers that are compatible with Apache licensing.  Note that Maria is based on Drizzle. 

Drizzle is BSD licensed which is a permissive license compatible with Apache.  [https://mvnrepository.com/artifact/org.drizzle.jdbc/drizzle-jdbc].  The git is [https://github.com/krummas/DrizzleJDBC] and there are four to five active devs but very little activity as of late.  It may be that this is a sign of stabilty as downloads are now above 12M. 

Oracle's Connector J  [https://github.com/mysql/mysql-connector-j] has four active devs, two of whom are responsible for most of the PRs. 

I hope this is useful. 


Reference also: [https://www.geeksforgeeks.org/jdbc-drivers/]  (Type 1 through 4 explained) 

[https://mariadb.com/kb/en/library/about-mariadb-connector-j/] 

> Replace MariaDB driver with drizzle as JDBC driver
> --------------------------------------------------
>
>                 Key: FINCN-26
>                 URL: https://issues.apache.org/jira/browse/FINCN-26
>             Project: Fineract Cloud Native
>          Issue Type: Task
>          Components: fineract-cn-mariadb
>            Reporter: Myrle Krantz
>            Priority: Blocker
>
> Fineract CN currently depends on 'org.mariadb.jdbc:mariadb-java-client:1.4.3' as our JDBC driver.  It's for our connection to an SQL database, and can be used for MySQL as well as MariaDB. This component is licensed as LGPL, and therefore, needs to be replaced before we release.  The current suggestion is to replace it with drizzle.  Other suggestions are also welcome.
> Why can't we have dependencies to LGPL software? This sequence of events would be bad:
> 1.) We include LGPL software in our release.
> 2.) Our code, including the LGPL dependency is included in proprietary code of CompanyOmega
> 3.) Some judge somewhere decides that the "firewall" separating our code from the LGPL isn't strong enough to call prevent the viral aspects of LGPL from taking effect.
> 4.) CompanyOmega's proprietary code is now all open source and they go out of business.
> It's not a likely sequence, but because of the size of the negative outcome, we avoid it by not including LGPL (or any other Category X software) in our releases.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)