Also make note of how much of your code really needs to be dynamic. I don't know what your app does - but if the data that it is yanking from the DB isn't changing that much over time, then you can create static pages that will obviously be far faster and put less of a load on the server.

This is worthless in some environments where every query is different, or where the data is changing every 2 seconds.

But if by chance your app is something where the data is slow to change over time, you can have scripts create static pages every morning when the load on the server is slow - then let the users navigate the static pages.
Good if your users come in to look at data briefly and rarely (once a day and the data hasn't changed since yesterday).
Lousy if users are using the app all day long, and every page that they load involves more data being changed and requiring more updates.


Of all the web apps that I've worked on and/or written, there are some that looking back on it, we could/should have done that - and then there are many on the other hand that can't ever do that b/c it just won't fit in the environment.
I'm curious as to what your app does

-------------------------------------------------------------------
There are some odd things afoot now, in the Villa Straylight.