[Lift] Re: Does memcache fit in here somewhere?
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 On Jan 6, 10:27 pm, Bob Eastbrook baconeater...@gmail.com wrote: I'm keeping my eye on Lift, but I'm primarily a PHP guy as far as paying the bills goes. I've got a slightly better high-level understanding of things now versus a month or so ago, but I'm not sure where caching fits into the picture. In the LAMP world, it's standard practice to put memcache in front of your database server. It's pretty much a cache everything philosophy. Is this not encouraged with Lift? I assume there are more caching choices in the Java world such as ehcache, but I don't see them mentioned on the list. Bob --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Does memcache fit in here somewhere?
David, What is the actual status of scala.actors.remote. I mean if you want to distribute your application, do you still need to use JMS or AMQP or something like that? Thx, Ramzi On Wed, Jan 7, 2009 at 5:15 AM, David Pollak feeder.of.the.be...@gmail.com wrote: Bob, memcached is failure. Using memcached means that the application stack has somehow failed to deliver the appropriate caching and concurrency tools. Scala and Scala Actors provide a powerful mechanism for building domain appropriate caching. Please look at this presentation. Thanks, David On Tue, Jan 6, 2009 at 7:27 PM, Bob Eastbrook baconeater...@gmail.com wrote: I'm keeping my eye on Lift, but I'm primarily a PHP guy as far as paying the bills goes. I've got a slightly better high-level understanding of things now versus a month or so ago, but I'm not sure where caching fits into the picture. In the LAMP world, it's standard practice to put memcache in front of your database server. It's pretty much a cache everything philosophy. Is this not encouraged with Lift? I assume there are more caching choices in the Java world such as ehcache, but I don't see them mentioned on the list. Bob -- 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 liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Does memcache fit in here somewhere?
Ramzi, Remote Actors are fragile. AMQP (RabbitMQ) or ActorD ( http://code.google.com/p/actord/) are better options. ActorD has the advantage of having a memcached ABI (wire protocol interface) and can make it easy to migrate logic out of PHP or Rails code into Scala Actors. Thanks, David On Wed, Jan 7, 2009 at 7:23 AM, Ramzi BEN YAHIA ramzi.benya...@gmail.comwrote: David, What is the actual status of scala.actors.remote. I mean if you want to distribute your application, do you still need to use JMS or AMQP or something like that? Thx, Ramzi On Wed, Jan 7, 2009 at 5:15 AM, David Pollak feeder.of.the.be...@gmail.com wrote: Bob, memcached is failure. Using memcached means that the application stack has somehow failed to deliver the appropriate caching and concurrency tools. Scala and Scala Actors provide a powerful mechanism for building domain appropriate caching. Please look at this presentation. Thanks, David On Tue, Jan 6, 2009 at 7:27 PM, Bob Eastbrook baconeater...@gmail.com wrote: I'm keeping my eye on Lift, but I'm primarily a PHP guy as far as paying the bills goes. I've got a slightly better high-level understanding of things now versus a month or so ago, but I'm not sure where caching fits into the picture. In the LAMP world, it's standard practice to put memcache in front of your database server. It's pretty much a cache everything philosophy. Is this not encouraged with Lift? I assume there are more caching choices in the Java world such as ehcache, but I don't see them mentioned on the list. Bob -- 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 -- 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 liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Does memcache fit in here somewhere?
Thanks for posting the presentation. Very informative, plus I love the chalkboard look and feel! Dan On Jan 7, 9:10 am, David Pollak feeder.of.the.be...@gmail.com wrote: Ramzi, Remote Actors are fragile. AMQP (RabbitMQ) or ActorD (http://code.google.com/p/actord/) are better options. ActorD has the advantage of having a memcached ABI (wire protocol interface) and can make it easy to migrate logic out of PHP or Rails code into Scala Actors. Thanks, David On Wed, Jan 7, 2009 at 7:23 AM, Ramzi BEN YAHIA ramzi.benya...@gmail.comwrote: David, What is the actual status of scala.actors.remote. I mean if you want to distribute your application, do you still need to use JMS or AMQP or something like that? Thx, Ramzi On Wed, Jan 7, 2009 at 5:15 AM, David Pollak feeder.of.the.be...@gmail.com wrote: Bob, memcached is failure. Using memcached means that the application stack has somehow failed to deliver the appropriate caching and concurrency tools. Scala and Scala Actors provide a powerful mechanism for building domain appropriate caching. Please look at this presentation. Thanks, David On Tue, Jan 6, 2009 at 7:27 PM, Bob Eastbrook baconeater...@gmail.com wrote: I'm keeping my eye on Lift, but I'm primarily a PHP guy as far as paying the bills goes. I've got a slightly better high-level understanding of things now versus a month or so ago, but I'm not sure where caching fits into the picture. In the LAMP world, it's standard practice to put memcache in front of your database server. It's pretty much a cache everything philosophy. Is this not encouraged with Lift? I assume there are more caching choices in the Java world such as ehcache, but I don't see them mentioned on the list. Bob -- Lift, the simply functional web frameworkhttp://liftweb.net Collaborative Task Managementhttp://much4.us Follow me:http://twitter.com/dpp Git some:http://github.com/dpp -- Lift, the simply functional web frameworkhttp://liftweb.net Collaborative Task Managementhttp://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 liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Does memcache fit in here somewhere?
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 ? There seems to have been talk of Terracotta integration at one point. Is that still in the works? Or, would we just rely on the load balancer to step in because an Actors cache wouldn't be clustered? 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. Bob On Jan 7, 5:22 am, TylerWeir tyler.w...@gmail.com 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 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Does memcache fit in here somewhere?
On Wed, Jan 7, 2009 at 6:47 PM, Bob Eastbrook baconeater...@gmail.comwrote: 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 tyler.w...@gmail.com 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 liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Does memcache fit in here somewhere?
On Tuesday 06 January 2009 20:15, David Pollak wrote: Bob, memcached is failure. ... Please look at this presentation. That's rather elliptic. Is there something less terse to go with it? Some more detailed paper or exposition of its thesis, perhaps? Thanks, David Randall Schulz --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
