Hi, I like the idea of: * Scalable storage: what would a storage api look like that's intended to map to scalable storage (column stores, key/value stores, partitioned stores)?
It would be interesting to think about an interface to SimpleDB. However, I think the other two items would duplicate work elsewhere and/or be too narrow in scope. For example, if you want to deploy a lift application on Amazon EC2 then checkout the Cloud Tools open-source project www.cloudtools.org. Similarly, Cloud Foundry (www.cloudfoundry.com) provides application monitoring and management. Chris On Mon, Feb 16, 2009 at 11:46 AM, mighdoll <[email protected]> wrote: > > Thinking about Lift after 1.0, I was thinking one possible direction > would be to specialize in cloud computing... > > Reading the following paper on the challenges of cloud computing gave > me a few quick ideas > http://www.eecs.berkeley.edu/Pubs/TechRpts/2009/EECS-2009-28.pdf: > > * Scaling quickly: perhaps lift could build (or integrate with) a > layer to detect load and deploy more/fewer instances semiautomatically > * Scalable storage: what would a storage api look like that's intended > to map to scalable storage (column stores, key/value stores, > partitioned stores)? > * Deployment: perhaps lift should release deployment scripts, or even > EC2 VM instances? > > Food for thought. > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
