BlitzDB is now in Drizzle’s Trunk Repository
Happy to announce that BlitzDB has been merged with Drizzle’s Trunk.
As much as I’m excited, it’s time to come back to reality. This merge is merely a beginning. There is much more work that needs to be done to BlitzDB such as ensuring stability by adding more tests, find bugs, and eliminate them. I’m hoping that the likelihood of bugs being found will increase due to this merge. Admittedly, I want to hack on fancy (yet important) things like auto recovery but I’m going to resist doing this until I’m truly satisfied with the quality of BlitzDB. My plan is to have BlitzDB rock solid by Drizzle’s Beta release.
The review process to get BlitzDB into Drizzle was straight forward and smooth. This is mostly due to the fact that the community was very supportive about testing. Folks like Stewart Smith and Patrick Crews from Rackspace pointed out several bugs that I would not have found myself. I’m certainly lucky to have a supportive professional QA engineer (looking at you Patrick) to test out and give punishment to BlitzDB.
All I’ll be doing on BlitzDB for the next couple of weeks is debugging and refactoring to improve readability. What I need more of at the moment is test cases on JOINs that are likely to be used in practice. If you have a good test case, I would greatly appreciate it!
Congrats Toru!.
This was something Drizzle community was waiting to happen.
Thanks a lot
Blitzdb is not a fork of Drizzle. But part of Drizzle now onwards. am i right?
Hi Jobin,
Thanks. I’ll continue developing BlitzDB in it’s own tree. Working directly with Drizzle’s tree has it’s advantages but the commit log can be “noisy”. I think it’s easier to visualize the progress by working in BlitzDB’s own tree and get Drizzle to merge the updates.
Hi Toru,
Congrats for the merge and thanks for the BlitzDB. This was much needed, a general purpose and modern from scratch design borrowed from cool KV stores.
Do you have plans to port to MySQL for much more broad audience? I hope you do.