You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@esme.apache.org by "Ethan Jewett (JIRA)" <ji...@apache.org> on 2011/09/07 08:49:13 UTC
[jira] [Updated] (ESME-358) Allow for optional use of Redis as a
datastore
[ https://issues.apache.org/jira/browse/ESME-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ethan Jewett updated ESME-358:
------------------------------
Description:
The idea is to provide the option 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
was:
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
Summary: Allow for optional use of Redis as a datastore (was: Port the ESME to REDIS)
Just updating the issue to indicate that the idea is to make it possible (though not required) to use Redis as a backing store, or as a backing store just for messages. I think this reflects the discussion I saw on the list.
In my opinion it would be a bad idea to make Redis (or any other NoSQL solution) required to run ESME, as RDBMSes are much more widely used and understood and will meet the requirements of a very large percentage of ESME use cases.
> Allow for optional use of Redis as a datastore
> ----------------------------------------------
>
> 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 provide the option 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