esme-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jack Park <>
Subject Re: 1.4 planning
Date Mon, 05 Sep 2011 20:11:02 GMT
At the moment, I'm not sure about creating a Jira for it, but I am 
working on it.  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

When I get something that works, I'll toss it up to github and ask 
others to polish the work of this scala beginner.

My present thinking is that user modeling is still handled in an RDBMS 
(though, I suppose, even there it's possible to run into scaling problems)


On 9/2/2011 10:25 AM, Ethan Jewett wrote:
> That's a good point. Nothing with that level of scale is currently in
> the realm of possibility for our use-cases, but as machine-generated
> data becomes more prevalent it is going to become more of a problem.
> Want to create a Jira for it and assign it to the backlog? If you have
> some ideas about how this should be done or want to work on a
> prototype, go for it :-)
> Ethan
> On Fri, Sep 2, 2011 at 6:07 PM, Jack Park<>  wrote:
>> The interesting question for me is: how many records can you store in an
>> RDBMS before you have to think about scale up issues? I wrote a trivial
>> microblog in Java using Redis; I think there is a candidate fit.
>> Cheers
>> Jack
>> On 9/1/2011 11:53 PM, Ethan Jewett wrote:
>>> It's certainly an interesting idea, and Lift does have some built-in
>>> capabilities here in the form of the Record module. It would be a
>>> pretty significant migration.
>>> An interesting question to explore: Would this give us a performance
>>> boost in some scenarios?
>>> Cheers,
>>> Ethan
>>> On Thu, Sep 1, 2011 at 10:54 PM, Jack Park<>
>>>   wrote:
>>>> Somewhat beyond 1.4, I'd like to ask about persistence other than RDBMS.
>>>> For
>>>> instance, in microblogging, there is some evidence that Redis can provide
>>>> a
>>>> scalable datastore.
>>>> Thoughts?
>>>> Cheers
>>>> Jack
>>>> On 8/29/2011 11:27 PM, Richard Hirsch wrote:
>>>>> I've been thinking about the next release and wanted to start
>>>>> collecting ideas for features for this release.
>>>>> There are some tasks in Jira [1] but that list isn't complete:
>>>>> Here are some other ideas:
>>>>> * Integration with Akka / Apache Camel
>>>>> * Simplification of URLs
>>>>> * Change Web UI to deal with new icon
>>>>> Any one else have other ideas / suggestions?
>>>>> D.
>>>>> [1]

View raw message