You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@esme.apache.org by "Dick Hirsch (JIRA)" <ji...@apache.org> on 2011/09/07 08:01:15 UTC
[jira] [Created] (ESME-358) Port the ESME to REDIS
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
Re: [jira] [Created] (ESME-358) Port the ESME to REDIS
Posted by Imtiaz Ahmed H E <in...@gmail.com>.
Well...for one thing, that's evidence that you can construct a 30+
word sentence. Otherwise let's wait and see...! :-)
On 9/9/11, Jack Park <ja...@topicquests.org> wrote:
> Something different (perhaps only for me) in the sense that my venture
> into attaching Redis to Lift moves away from Record or Mapper and all
> the great features they offer, towards something different from that,
> perhaps closer to a one-to-one mapping of my Java code into Scala.
> How's that for a one-sentence response?
>
> Jack
>
> On 9/9/2011 5:30 AM, Richard Hirsch wrote:
>> I'm curious - what do you mean by "something different seems to be
>> emerging"
>>
>> D.
>>
>> On Fri, Sep 9, 2011 at 6:14 AM, Jack Park<ja...@topicquests.org>
>> wrote:
>>> 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
>>>>
>>>>
>>>
>
--
Sent from my mobile device
Re: [jira] [Created] (ESME-358) Port the ESME to REDIS
Posted by Jack Park <ja...@topicquests.org>.
Something different (perhaps only for me) in the sense that my venture
into attaching Redis to Lift moves away from Record or Mapper and all
the great features they offer, towards something different from that,
perhaps closer to a one-to-one mapping of my Java code into Scala.
How's that for a one-sentence response?
Jack
On 9/9/2011 5:30 AM, Richard Hirsch wrote:
> I'm curious - what do you mean by "something different seems to be emerging"
>
> D.
>
> On Fri, Sep 9, 2011 at 6:14 AM, Jack Park<ja...@topicquests.org> wrote:
>> 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
>>>
>>>
>>
Re: [jira] [Created] (ESME-358) Port the ESME to REDIS
Posted by Richard Hirsch <hi...@gmail.com>.
I'm curious - what do you mean by "something different seems to be emerging"
D.
On Fri, Sep 9, 2011 at 6:14 AM, Jack Park <ja...@topicquests.org> wrote:
> 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
>>
>>
>
Re: [jira] [Created] (ESME-358) Port the ESME to REDIS
Posted by Jack Park <ja...@topicquests.org>.
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
>
>
[jira] [Updated] (ESME-358) Allow for optional use of Redis as a
datastore
Posted by "Ethan Jewett (JIRA)" <ji...@apache.org>.
[ 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