A MySQL Core Kernel?

What Would It Look Like?

This session is an open discussion about what two things:

1. What a MySQL Core Kernel would be composed of
2. Steps to take in order to modularize the MySQL server code to allow for a more pluggable architecture

A Core Kernel

It's my strong belief that having a modularized core server kernel would allow for greatly increased innovation and contributions from the MySQL developer community. There has been quite a bit of press and interest around the 5.1 pluggable storage engine architecture and FULLTEXT plugins, but this is just the start of an effort to make the server more extensible. Having a well-defined core kernel which provides extension points for plugins and modules would allow for the following:

1. Ability for developers (both community and MySQL AB) to isolate code changes to a module, which subsequently enables functional pieces (such as a storage engine, a FT plugin, or other features) to be versioned separately and their release cycle freed from the confines of the main server tree, greatly streamlining the build process
2. Development of an ecosystem of plugins and modules, similar to the Apache module ecosystem or the Firefox extension/add-on community

But, before this can happen on a large scale -- i.e. not just for storage engines or FT plugins -- a core set of kernel components needs to be documented and discussed. This session aims to be a brainstorming session to identify those core pieces.

Interested in Participating? Put Your Name Down

• Jay Pipes
• Paddy Sreenivasan
• Jeremy Cole
• Kapil Surlaker
• Yoshinori Matsunobu
• Kristofer Pettersson