Let me reply here before I get around to playing with JIRA. I'd like to explain my motivations, which might clarify a few things. Firstly, I do not advocate anything like a wholesale switch from RDBMS to NoSQL; that's going to depend on scenarios, and not all scenarios (perhaps just a few) drive such a need. My motivations create an opportunity to keep such scalability in mind. In my own use cases, I imagine leaving user persistence to RDBMS and persisting nodes and timelines in NoSQL; since I built a tiny microblog platform in pure Java that used Redis, that's where my thinking started.

The project du jour is not a microblog, but, instead, a "structured conversation" platform. It's pre-pre-pre-alpha prototype, and is online at http://www.topicspaces.org:8888/; it's written in Lift, and is being used to test UI and data structure ideas that I think might find their way into a microblog--specifically, say, an extended ESME, some day in the future. I am bringing up Redis in that platform now; it's becoming clear that this is not your father's Mapper application; something different seems to be emerging.

Cheers
Jack

On 9/6/2011 11:01 PM, Dick Hirsch (JIRA) wrote:
Port the ESME to REDIS
----------------------

                  Key: ESME-358
                  URL: https://issues.apache.org/jira/browse/ESME-358
              Project: Enterprise Social Messaging Environment (ESME)
           Issue Type: Improvement
           Components: Server
     Affects Versions: 1.3
             Reporter: Dick Hirsch
              Fix For: Backlog, 1.4


The idea is to replace the existing RDBMS with REDIS.

Perhaps via an option in the default properties?

Here are details from the mailing list:

I started with https://github.com/indrajitr/scala-redis and, thanks to 
conversations with Indrajit, have learned that I can craft what I call 
RedisModel (an object) that holds a live instance of RedisClient and presents a 
useful API for doing timelines and nodes. I'm working on that now.  RedisClient 
must be configured in Boot.scala

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


Reply via email to