[DERBY-3351] Implement a Pluggable Storage Engine Architecture in Derby

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: Services, SQL, Store
• Labels: derby_triage10_10
• Urgency: Normal
• Assignee: Unassigned
• Reporter: Dibyendu Majumdar
• Created: 24/Jan/08 22:58
• Updated: 18/Jul/13 09:46

Description

My aim is to create a pluggable storage engine architecture for Derby, so that the default store implementation can be replaced with alternative storage engines. I have created my own storage engine which I would like to use with Derby's SQL layer, so that is a motivation. But I also think that this will benefit the community, and could lead to a pluggable storage engine architecture similar to that of MySQL.

I am not yet sure where the storage engine boundary should lie. I would welcome input in this area.

Issue Links

• is related to: DERBY-3450 Reduce module dependencies in Derby