"CodernityDB pure python, NoSQL, fast database" Is the fact that it is written in "pure Python" really the most important thing to reenforce after the name of the product itself? Why would I use this over established products like Riak, Redis, MongoDB, etc?
If you look at the speed benchs they compare it to kyoto cabinet. I think that CodernityDB is meant to be embedded and is thus only interesting to python people. In that case the advantage would be to avoid the compilation step on intall that kyoto cabinet or sqlite would incur. It's a library database like sqlite and kyoto cabinet
CodernityDB — pure Python, NoSQL, fast database
11–20 of 52 posts
Re: CodernityDB — pure Python, NoSQL, fast database
#12Since these questions will inevitably come up: - You fsync yourself to ensure durability. I can't see at a glance what fsync settings are used for the speed tests. - It's not transactional, although single operations are atomic. - Indexes operate on a single-writer, multiple reader basis. - No traditional joins, although you can of course write a procedural function that joins for you.
The other attributes i'm not too fussed about personally, i figure i can always work around them or face the question "am i using the right tool for this job?" but the fsync one still gives me the heeby-jeebies (even though it's never bitten me despite many many TBs of data).
Cassandra does periodic fsync's (although it can be configured). I understand HBase and Mongo have similar shennanigans.
Re: CodernityDB — pure Python, NoSQL, fast database
#13"Indexes tries to reuse as much space as possible, because metadata size is fixed, during every write operation, if index finds metadata marked as removed or so, it reuses it - writes new data into that place."
I'm curious how this is implemented.
Re: CodernityDB — pure Python, NoSQL, fast database
#14Re: CodernityDB — pure Python, NoSQL, fast database
#15The only thing that turns me off to a product more than a poor website is poor English in the documentation. If English isn't your primary language, PLEASE get someone that speaks it fluently to either write your docs, translate your docs, or edit what you've written.
Re: CodernityDB — pure Python, NoSQL, fast database
#16"CodernityDB pure python, NoSQL, fast database" Is the fact that it is written in "pure Python" really the most important thing to reenforce after the name of the product itself? Why would I use this over established products like Riak, Redis, MongoDB, etc?
I've been looking at DBM::Deep (one of perl's equivalent to CodernityDB) and App::FatPacker recently just for this case (install a script on some Macs with only Perl being needed requirement).
ref: https://metacpan.org/module/DBM::Deep | https://metacpan.org/module/App::FatPacker
Re: CodernityDB — pure Python, NoSQL, fast database
#17"CodernityDB pure python, NoSQL, fast database" Is the fact that it is written in "pure Python" really the most important thing to reenforce after the name of the product itself? Why would I use this over established products like Riak, Redis, MongoDB, etc?
It is for me. It's the most unique attribute about the project. Fast? Yawn. NoSQL? Yawn.
Re: CodernityDB — pure Python, NoSQL, fast database
#18Re: CodernityDB — pure Python, NoSQL, fast database
#19"CodernityDB pure python, NoSQL, fast database" Is the fact that it is written in "pure Python" really the most important thing to reenforce after the name of the product itself? Why would I use this over established products like Riak, Redis, MongoDB, etc?
Re: CodernityDB — pure Python, NoSQL, fast database
#20The only thing that turns me off to a product more than a poor website is poor English in the documentation. If English isn't your primary language, PLEASE get someone that speaks it fluently to either write your docs, translate your docs, or edit what you've written.