Hi ... new to Scala and Lift. I'm having trouble understanding how to think about a project with a horizontally scaled database. I guess people call this "sharding" these days? My existing app uses PHP, no framework, and no O-R mapping. It's all PHP/MySQL with SQL statements. Some O-R mappers seem to partially support sharding and I'm wondering if Lift's does? Adding AJAX to this app is not going to be easy, and I'm considering a rewrite now that I know a little more about what I'm doing. Plus, I'm kind of bored with PHP. When it comes to database access, does Lift avoid the scalability problems I hear Rails has?
Or, is there a better way do horizontally scale these days? I see that SQL Server supports distributed partition views, which I'm still learning about. Something at the database server side of things which transparently handles the horizontal scale-out would be great. Not sure if distributed partition views actually do this though. This also looks like it'd make my life easier: http://www.hivedb.org/ thanks, Bob --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
