Hi Esteban,
why I like it:
- it is similar to SQLite3 very small, just one DLL or shared lib
- very portable across many platforms (DB is independent from byte order or 32bit vs. 64 bit)
- easy to use
- there is already a wrapper now for Pharo :)
"UnQLite is a standard key/value store similar to BerkeleyDB, Tokyo Cabinet, LevelDB, etc. but, with a rich feature set including support for transactions (ACID), concurrent reader, etc. "
http://unqlite.org/arch.htmlhttp://www.methodsandtools.com/tools/unqlite.php
Thanks
Torsten
Gesendet: Donnerstag, 16. Januar 2014 um 14:08 Uhr
Von: "Esteban Lorenzano" <estebanlm@gmail.com>
An: "Torsten Bergmann" <astares@gmx.de>
Cc: "Pharo Development List" <pharo-dev@lists.pharo.org>
Betreff: Re: Voyage backends
Ho Torsten,
well� I planned Riak and maybe Tokyo and Omnibase (but when I find the time� not much this days). I never thought about UnQLite (and also I never hear about it before :P )
cheers,
Esteban
On 16 Jan 2014, at 14:03, Torsten Bergmann <astares@gmx.de> wrote:
Hi Esteban,
if I understood correctly Voyage is primarily an abstraction layer to access
NoSQL databases. Currently MongoDB or the image can be used as a backend.
Are there any other backends available or planned (for instance to UnQLite using
PUnqlite [1]).
As UnQLite is an embeddable database of really small size I guess it will be
as sucessful for the NoSQL world as SQlite3 was for the relation DBMS world
and supporting it as one possible backend for Voyage might be a real plus.
At least I see that MongoDB is 102MB to install before one can use it and
unqlite library [2] is only a few KB ;)
So it is easier to package, deploy, ... - I havent checked the other features
of Mongo vs. PunQlite so far.
Any comments about backends in general or UnQlite in particular?
Thx
T.
[1] http://forum.world.st/ANN-PunQLite-a-new-NoSQL-wrapper-for-Pharo-td4732162.html
[2] https://github.com/mumez/PunQLite/tree/master/binary