Dear Wiki user, You have subscribed to a wiki page or wiki category on "Directmemory Wiki" for change notification.
The "ProposedRoadmap" page has been changed by RaffaeleGuidi: http://wiki.apache.org/directmemory/ProposedRoadmap?action=diff&rev1=2&rev2=3 * '''Lateral storage''' (distributed or replicated) - A possible way to do this: hazelcast for map distribution and Apache Thrift for intra node communication (node a needs an item stored in node b and then asks for it). I'm not sure hazelcast would perform as well as Guava with multi million item maps, it has to be thoroughly tested for perfomance and memory consumption - should hazelcast not fit the performance requirement we should finda an alternative way to distribute/replicate the map across nodes. jgroups with multicasting would be perfect but it's LGPL (well, JCS uses it) and, of course, a custom, maybe thrift based, distribution mechanism could be written ad-hoc == Integration with other products == Providing plugins, integration or just support with/for other technologies/products would of course spread adoption. These are the first few that pop in my mind at the moment - * '''Apache Cayenne integration''' - do I need to tell why? ;) + * '''Apache JCS integration''' - as an off-heap memory plugin + * '''Apache Cayenne integration''' - as a 2nd level query cache * '''Play! Framework integration''' - because I simply love play! and use it in other side projects whenever I need a web/mobile front-end * '''Memcached (like) integration''' - DirectMemory can be seen as an embedded memcached and adoption its protocol would be a good fit for replacing it in distributed scenarios most of all when it's used by java applications * '''Scala, Clojure''' and other jvm languages integration - emerging technologies that deserve attention. Should I have 48 hours days I would use the other 24 to improve my scala skills and rewrite DirectMemory can with it
