On Wed, Jan 7, 2009 at 6:47 PM, Bob Eastbrook <[email protected]>wrote:
> > > I've read most of what you guys have up there so far. Before I knew > about it, I was pretty much lost. Very much looking forward to the > final product. > > My favorite thing about Lift is the use of Snippets. I work in PHP > primarily without a framework, and I don't mind writing SQL but it's > always a struggle adding new features as consumer tastes change. > Component-based development gets me excited. > > The one thing I can't quite grasp yet is how I can move away from > memcache and use Actors. Thanks for that presentation though, David. > Is this the general strategy: > http://scala-blogs.org/2007/12/i-love-scala-actors.html > ? I think that post represents a notion rather than a strategy. But, yes, the idea of putting your business and persistence and caching logic in one place is the overall strategy. > > > There seems to have been talk of Terracotta integration at one point. > Is that still in the works? No. There are two operational modes for Terracotta... one is mesh and the other is hub and spoke where all messages have to flow through a hub. In order to use Actors, one has to use the hub/spoke mode and that means your world is going through a single machine. That's not scalable. > Or, would we just rely on the load > balancer to step in because an Actors cache wouldn't be clustered? You would distribute the Actors in the same way you distribute memcached instances... with some sort of consistent hashing mechanism. Alternatively, there are ways of meshing a DNS style lookup mechanism. > > > Having a clear solution of how to scale would be pretty interesting to > most PHP developers I know. Most of our conversations deal less with > PHP and more with memcache and MySQL replication. How big an app are you building? I've Twitter clone that could handle Twitter's traffic through mid-2008 on a single box based on Lift, Scala, and Actors. You'd be surprised how much "stuff" that you can run fast in a single JVM on a single box. Another benchmark is Buy a Feature which was able to serve a sustained 700 pages/sec on a single EC2 "Large" instance. If you're going to build a Twitter or WikiPedia or Facebook scale app, please give me a call and I can consult and help you. If you're building a site that can server 100-500 pages/sec, you should be fine with Lift, Scala, Actors and a single JVM. Thanks, David > > > Bob > > > On Jan 7, 5:22 am, TylerWeir <[email protected]> wrote: > > Hey Bob, less about memcached and more about Lift in general, take a > > look at the book, Marius, Derek and I are writing: > http://github.com/tjweir/liftbook/tree/master > > > > We'd love to get your feedback as a PHP guy. > > > > Thanks, > > Tyler > > > > -- Lift, the simply functional web framework http://liftweb.net Collaborative Task Management http://much4.us Follow me: http://twitter.com/dpp Git some: http://github.com/dpp --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
