Lift and Goat Rodeo

[David Pollak <fe...@gmail.com>]

Folks,

At the end of the Scala Lift Off, after I finished my third beer, Martin
Odersky came over to me and asked, "so, what's the future of Lift?"

I gave a hand-waving answer about the features for 1.1.  But Martin is not a
hand-waving kind of guy and I think I owe him and the other folks in the
Scala and Lift communities more.

There's a lot more that's necessary for web app development than Lift, an
abstraction to the HTTP request/response cycle, can provide.

Over the last couple of years, I've been noticing trends in web development,
in the needs of my various consulting gigs, and in some other projects.
It's clear to me that it's time for a unified data and data management model
that goes beyond OR mapping and that is scalably transactional.  I've put
together a model that looks to the developer like STM but is backed with
ZooKeeper and Cassandra.  I've blogged about it at
http://blog.lostlake.org/index.php?/archives/94-Lift,-Goat-Rodeo-and-Such.html

Just as my web framework manifesto was the genesis of what has become Lift,
I hope that my notions and ramblings in this blog post will become concrete,
usable code over the next few months and a solid platform for building the
next generation of web systems over the next few years... all built with
Scala at their core.

Thanks,

David

-- 
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Git some: http://github.com/dpp

Re: Lift and Goat Rodeo

[Esko Luontola <es...@gmail.com>]

David Pollak <fe...@...> writes:
> It's clear to me that it's time for a unified data and data management model
> that goes beyond OR mapping and that is scalably transactional.  I've put
> together a model that looks to the developer like STM but is backed with
> ZooKeeper and Cassandra.  I've blogged about it at
> http://blog.lostlake.org/index.php?/archives/94-Lift,-Goat-Rodeo-and-Such.html
> 

Interesting post. I'm also working on a system that tries to solve persistence, 
scalability and transactionality. It's meant for the needs of online games, 
which means low latency, 50% write load, mostly local data access patterns, high 
consistency requirements, but allows loosened durability. I suppose that typical 
web applications have different kind of characteristics, but maybe there are 
some ideas that can be shared.

You can read more about my project at http://dimdwarf.sourceforge.net/ - read 
from the front page "How does it work?", "Project Goals" and the two blog posts 
that are linked under "Articles about Dimdwarf". Right now it's at pre-alpha 
stage and I've been too busy this year to work on it, but toward the end of this 
year I should be able to continue its development.