StrokeDB: what's up?
I must confess. We've committed a serious sin. We haven't had a single commit in StrokeDB repository for almost two months. Sorry.
So... one may wonder whether StrokeDB is still alive. Well, yes it is. Though we have significant changes in our plan and approach.
As for now, we consider existing StrokeDB as a first prototype — it has both cool things and a lot of crappy code. So most probably the existing version will perish.
However, we are learning lessons of that awesome development cycle and trying to produce something more clean, both conceptually and code-wise. One of the versions we've started working on, is Oleg's strokedb-core, an attempt to minimize StrokeDB's essential core functionality and therefore get a way more modular and simpler thing.
That said, I am still trying to assemble my thoughts about my initial StrokeDB experience and come out with cures for some problems. That might mean yet another "rewrite" branch I can start anytime soon in order to consolidate my updated vision.
Another change we're working on is getting rid of our custom storages and usage of more proven things, like TokyoCabinet. As far as you can understand that leads to elimination of skiplist and therefore less code. Which is pretty good anyway.
So, to recap, our plan is to:
- Modularize core
- Consolidate updated data organization vision
- More reliable storage
Unfortunately, the deadline date is open. We have no idea when it will be done.
I have a bit busy summer and I still can't work full-time on StrokeDB (and will not be able for a substantial period, unfortunately), but be assured, I am definitely not going to throw this stuff away. Neither does Oleg.
Stay tuned! :)
Recent Comments