Sam Ritchie
Sam Ritchie
From the Doozerd page: https://github.com/ha/doozerd ``` text Doozer is a highly-available, completely consistent store for small amounts of extremely important data. When the data changes, it can notify connected clients...
The notion of a VersionedStore would make it easy to create a distributed read-only database backed by storehaus stores that loaded themselves off of disk. ``` scala import com.twitter.util.{ Duration,...
We should have a default thrift service that a storehaus store of [ByteBuffer, ByteBuffer] can hook into on either end. Client and server implementations; the user can use a `ConvertedStore`...
This code would be really useful in a write-only abstraction (writing to Storm's collectors, for example). Related to #91
BufferingStore might accept a Timer as well and schedule a flush on some regular interval. This would require synchronizing access to the promise map and the wrapped store.
Looks like they've improved the way they handle client instantiation: https://github.com/twitter/finagle/blob/master/finagle-memcached/src/main/scala/com/twitter/finagle/Memcached.scala
This method of construction would make it easy to, say, instantiate a `TTLCache` with an `LRUCache`, gaining the semantics of both caches.
https://github.com/twitter/storehaus/blob/develop/storehaus-core/src/main/scala/com/twitter/storehaus/ReadableStore.scala#L70 This would allow the user to use injections and bijections. `flatMapValues` could still make this version available.
Clojure's core.cache has this to say: "Cached values will be referred to with SoftReferences, allowing the values to be garbage collected when there is memory pressure on the JVM." An...