Tokyo Cabinet vs MongoDb

[Ray Dookie]

Hi Guys,

I was playing with mongo for some time now, and then someone told me about Tokyo cabinet.

I was just wondering, if anyone here has used tokyo before?

If so, whats the main difference between these 2?...and When should I use one over the other?

Regards,

Ray.

[Rick R]

Tokyo cabinet is a very nice, efficient on-disk key/value store.
That's pretty much it.

MongoDB is a document database system, including network drivers, multiple indices, and a slew of other nifty features.
 
So if all you need is to store key/value pairs in-process, and not have additional indices, and not share with other applications, or you want to build all of those cool features yourself, use Tokyo Cabinet, otherwise, I'd recommend MongoDB.

--
We can't solve problems by using the same kind of thinking we used when we created them.
   - A. Einstein

[pcdinh]

I think that Redis (http://code.google.com/p/redis/) is more efficient
than Tokyo Cabinet

[Kless]

I think that each one has its own place.

In my case I'm going to use Redis to users sessions and also for data
related to authentication (groups, and permissions). Generally, Redis
is for data used very frecuently since that they're on memory but it
can be stored on disk (this is the big difference with memcached)

Tokyo Cabinet could be used to store data related to logging.

And MongoDB for all rest (user profiles and data of your web
application) :)

[Dan Lynch]

Have you tried MongoDB for user sessions and other high frequency
data?
We're using it now and its working really well, so just curious why
you would use redis.

We're using mongo capped collections for logging and its working well.
Well, we're using capped collections and then archiving.
But the capped work well for the last few days and searching, etc...

[Kless]

On 8 mayo, 11:40, Dan Lynch <danlync...@yahoo.com> wrote:
> Have you tried MongoDB for user sessions and other high frequency
> data?
> We're using it now and its working really well, so just curious why
> you would use redis.

No, I haven't. And I'm sure that Mongo can manage those data very well
but the Redis API is very simple and fills this place very well.

I'm finishing a plugin for Repoze.what to use Redis and has been very
fast (for Mongo it was harder).

I like Mongo and its API (it's awesome), but in my case I've found
that Redis goes very well to manage data related to authentication
since that it has functions to working with lists and sets.

http://code.google.com/p/redis/wiki/CommandReference
http://github.com/antirez/redis/blob/93ea375904fa2a5d1cab110698d15f43e63d84f1/client-libraries/python/redis.py

> We're using mongo capped collections for logging and its working well.
> Well, we're using capped collections and then archiving.
> But the capped work well for the last few days and searching, etc...

About logging I cann't say much until that I make tests about several
databases, as Tokyo Cabinet, Hypertable, and could be with Mondodb