Ahh just saw David beat me to it with the other reply :-) John Pletka <[email protected]> writes:
> It is a business application - lots of forms, reports, data lookups. I'm > not too concerned about the performance on a single node - at any given time > we'll probably have a max of 1000 requests a minute coming in which I've > seen Lift handle easily. The biggest problem is we need near 100% up-time. But you can have near 100% uptime with sticky sessions. What you can't have is High Availability (HA), ie. users won't notice when a server breaks. > That means having at least a second server in hot-standby mode > (preferably parallel production), and some way to do upgrades without > bringing the whole site offline. Doing rolling upgrades is never easy, even if you don't share state. You may have all this figured, but you need to account for different app versions running simultaneously, expanding/shrinking db upgrades etc. /Jeppe -- 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.
