esme-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jack Park <>
Subject Re: [jira] [Created] (ESME-358) Port the ESME to REDIS
Date Fri, 09 Sep 2011 04:14:08 GMT
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; 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.


On 9/6/2011 11:01 PM, Dick Hirsch (JIRA) wrote:
> Port the ESME to REDIS
> ----------------------
>                   Key: ESME-358
>                   URL:
>               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 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:

View raw message