Earlier quoted context omitted.
> If it were a website/webapp you'd still run into issues with bugs, security fixes. This was really true a few years ago, but changed as of late. Right now we are running all of our sites on a Sinatra-based engine on Heroku. It has no admin backend, no security fixes to make, nothing. There isn't even a database! The whole thing is compiled and cached. Any changes made on a live basis come through git or via a uniqu…
That's interesting but definitely not a global use case. Most apps will require some sort of bug fixes and security updates. Even the linux kernel requires security updates and I do think that's some tight code right there =) Not every app can be compiled-cached-served. I think 99% of them can't go that route.. Would love to see how you can run relatively dynamic code/functionality by the method you're suggesting.
I'm talking about the typical affiliate site that is SEO'd or run with PPC. Many of those don't require much and you can often do dynamic functionality without requiring a database.
I have one site where you can look up physical locations of the merchant. Instead of a database, there is a YAML file that is dumped into MemCache - doing a search hits that and I don't need to maintain any Postgres instances.