Hi
There are already some initiatives on this site, which point to the same direction:
Focus A: server load / response times
Focus B: integration with outer pages and content, even toher sites.
About Focus A:
How to avoid that high load situations get to much of a burden for the site engine?
Lets see:
under normal conditions every page and block produces several MySQL-requests, which is softened by different caching approaches: the general drupal cache and the new block cache for example.
But even these will produce database requests - eventhough less than "normal".
In a tough situation, where the bottleneck may not be the server itself, but the database connection, alternatives may be valuable, in order to reduce the overall load on the system.
So here is the thought I would like to share and eventuelly request not only Your opinion, but also some hand for coding the solution - which I can not do, because I am not a programmer.
Payment can be discussed.
1) Bottleneck nodes / feeds:
It was a simple excercise to see the impact in this topic.
The more modules and the more languages You install, the slower is the response.
Just for curiosity, we setup some 50 modules, plus some 20 languages, and almost fell asleep during while pages where produced and loaded : average times of over 67 seconds where no exception,
Serverload for node and feed request on shared hosting is therefore a hot topic.