Comments on: What’s the Point? http://yehudakatz.com/2009/02/12/whats-the-point/ Random Geek-Related Thoughts Wed, 08 Sep 2010 23:53:11 -0700 hourly 1 By: Alistair Holt http://yehudakatz.com/2009/02/12/whats-the-point/comment-page-1/#comment-15828 Alistair Holt Fri, 13 Feb 2009 00:28:40 +0000 http://yehudakatz.com/?p=217#comment-15828 Love it. Rack for key/value stores! Love it. Rack for key/value stores!

]]> By: GMFlash http://yehudakatz.com/2009/02/12/whats-the-point/comment-page-1/#comment-15827 GMFlash Thu, 12 Feb 2009 22:24:01 +0000 http://yehudakatz.com/?p=217#comment-15827 Moneta looks great! Have you considered supporting the memcached gem libmemcached library in addition to the memcache-client gem? From what I read this combination has better performance at the cost of being slightly harder to install since it has to compile. Moneta looks great! Have you considered supporting the memcached gem libmemcached library in addition to the memcache-client gem? From what I read this combination has better performance at the cost of being slightly harder to install since it has to compile.

]]> By: Dan Kubb http://yehudakatz.com/2009/02/12/whats-the-point/comment-page-1/#comment-15826 Dan Kubb Thu, 12 Feb 2009 22:05:01 +0000 http://yehudakatz.com/?p=217#comment-15826 Whoops.. I meant to say: "When Yehuda showed me his moneta API, I realized we could use a moneta store as an *IM* — with no code changes to DataMapper or Moneta whatsoever." IM == IdentityMap, which is something DataMapper uses internally to cache objects by their key in memory. When you use Model#get, DM checks the IM to see if you've already retrieved the object, and if so, just pulls it from there, saving you a call to the backend. This behavior only happens inside a repository() block, so it's opt-in only, but extremely useful. Originally the plan was to make some DataMapper::IdentityMap plugins for Memcache and Tokyo Cabinet, but I might just tell people to use a store that is Moneta-compatible instead. The advantage to this approach is that a Moneta store isn't DM-only, you could conceivably use it as a key/value cache for merb-cache, Rack::Cache or ActiveRecord among other things. Whoops.. I meant to say: “When Yehuda showed me his moneta API, I realized we could use a moneta store as an *IM* — with no code changes to DataMapper or Moneta whatsoever.”

IM == IdentityMap, which is something DataMapper uses internally to cache objects by their key in memory. When you use Model#get, DM checks the IM to see if you’ve already retrieved the object, and if so, just pulls it from there, saving you a call to the backend. This behavior only happens inside a repository() block, so it’s opt-in only, but extremely useful.

Originally the plan was to make some DataMapper::IdentityMap plugins for Memcache and Tokyo Cabinet, but I might just tell people to use a store that is Moneta-compatible instead. The advantage to this approach is that a Moneta store isn’t DM-only, you could conceivably use it as a key/value cache for merb-cache, Rack::Cache or ActiveRecord among other things.

]]> By: Dan Kubb http://yehudakatz.com/2009/02/12/whats-the-point/comment-page-1/#comment-15825 Dan Kubb Thu, 12 Feb 2009 21:56:50 +0000 http://yehudakatz.com/?p=217#comment-15825 The target with DataMapper's IdentityMap for the next minor release was using a subset of the Hash API anyway. When Yehuda showed me his moneta API, I realized we could use a moneta store as an I -- with no code changes to DataMapper or Moneta whatsoever. I love it when libraries base their API conventions on Ruby core classes. The target with DataMapper’s IdentityMap for the next minor release was using a subset of the Hash API anyway. When Yehuda showed me his moneta API, I realized we could use a moneta store as an I — with no code changes to DataMapper or Moneta whatsoever.

I love it when libraries base their API conventions on Ruby core classes.

]]> By: wycats http://yehudakatz.com/2009/02/12/whats-the-point/comment-page-1/#comment-15823 wycats Thu, 12 Feb 2009 19:07:39 +0000 http://yehudakatz.com/?p=217#comment-15823 Whoops... I forgot to include it in the original description of the API. Moneta has fetch, but it behaves like Ruby's #fetch (i.e. doesn't store the value) Whoops… I forgot to include it in the original description of the API. Moneta has fetch, but it behaves like Ruby’s #fetch (i.e. doesn’t store the value)

]]> By: Ben Burkert http://yehudakatz.com/2009/02/12/whats-the-point/comment-page-1/#comment-15822 Ben Burkert Thu, 12 Feb 2009 19:04:51 +0000 http://yehudakatz.com/?p=217#comment-15822 Why not add a #fetch method? Both Rails & Merb's caching implementation have a fetch method. Why not add a #fetch method? Both Rails & Merb’s caching implementation have a fetch method.

]]>