[GSOC-169] Apache ShardingSphere: Add the feature of switching logging framework

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Labels: ShardingSphere gsoc2023 mentor
• Assignee: Unassigned
• Reporter: Longtao Jiang
• Created: 16/Feb/23 15:31
• Updated: 21/Mar/23 08:08

Description

Apache ShardingSphere

Apache ShardingSphere is positioned as a Database Plus, and aims at building a standard layer and ecosystem above heterogeneous databases. It focuses on how to reuse existing databases and their respective upper layer, rather than creating a new database. The goal is to minimize or eliminate the challenges caused by underlying databases fragmentation.

Page: https://shardingsphere.apache.org
Github: https://github.com/apache/shardingsphere 

Background

ShardingSphere provides two adapters: ShardingSphere-JDBC and ShardingSphere-Proxy.

Now, ShardingSphere uses logback for logging, but consider the following situations:

• Users may need to switch the logging framework to meet special needs, such as log4j2 can provide better asynchronous performance;
• When using the JDBC adapter, the user application may not use logback, which may cause some conflicts.

 

Why doesn't the log facade suffice? Because ShardingSphere provides users with clustered logging configurations (such as changing the log level online), this requires dynamic construction of logger, which cannot be achieved with only the log facade.

Task

1. Design and implement logging SPI to support multiple logging frameworks (such as logback and log4j2)
2. Allow users to choose which logging framework to use through the logging rule

Relevant Skills

1. Master JAVA language

2. Basic knowledge of logback and log4j2

3. Maven

Mentor

Longtao Jiang, Committer of Apache ShardingSphere, [e-mail]

Trista Pan, PMC of Apache ShardingSphere, [e-mail]