CodernityDB — pure Python, NoSQL, fast database
labs.codernity.com
CodernityDB — pure Python, NoSQL, fast database
1–10 of 52 posts
Re: CodernityDB — pure Python, NoSQL, fast database
#2[deleted]
Re: CodernityDB — pure Python, NoSQL, fast database
#3I'd love to check this out this morning, but the page is unreadable using Safari on an iPhone. The table of contents stays floating above the body text, and takes up almost the whole screen.
Re: CodernityDB — pure Python, NoSQL, fast database
#4It would be helpful to add "How is this different from other NoSQL databases" to the FAQ.
Re: CodernityDB — pure Python, NoSQL, fast database
#5"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
#6Since 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.Re: CodernityDB — pure Python, NoSQL, fast database
#7"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?
perhaps it could be attracting devs, since python is a really awesome language to work with. but really, let's quit the snarkyness.
Re: CodernityDB — pure Python, NoSQL, fast database
#8Interesting, but I'd like to see how this compares to other NoSQL such as MongoDB.
Re: CodernityDB — pure Python, NoSQL, fast database
#9"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
Re: CodernityDB — pure Python, NoSQL, fast database
#10"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?
> Is the fact that it is written in "pure Python" really the most important thing to reenforce after the name of the product itself?
It's definitely a selling point for Python programmers, because it's so easy to use with your Python projects. You just set the package requirement and you're done, it will work in the same environment wherever your app works, upgrades are a piece of cake, no need to worry about platform support, permissions, etc.
f.ex. Whoosh (full-text search) gained a lot of traction in the Python world not because it was the fastest at the time nor the most full-featured (compared to the more mature Java-based ones), but because of convenience. Such solutions, even when they're not the most advanced player in the league, are great for starting up fast and pushing features out the door.
On a side note, it's a pleasure for me to see it's from Poland. Will test it out on a feature project in the next few days.