What architectures and frameworks should developrs know before designing a website?
What architectectures and frameworks should a developer know before designing a website?  Too many developers I have spoken with complain about the poorly written websites that they inherited.  Many of them end up re-writing sites to make them either more reliable or scalable.  What important things about architecture and frameworks should developers know before designing a website and what are some architectural mistakes that developers should avoid?


I am not talking about the technical aspects as explained in [this post][1], but rather architectural aspects such as clusters, message queues, frameworks, data partitioning, batch processing, etc.. What are the best practices for using such components and how should they be put togeteher to produce reliable, scalable and dependable websites?  


  [1]: http://stackoverflow.com/questions/72394/what-should-a-developer-know-before-building-a-public-web-site
What architectures and frameworks should developrs know before designing a website?
===

What architectectures and frameworks should a developer know before designing a website?  Too many developers I have spoken with complain about the poorly written websites that they inherited.  Many of them end up re-writing sites to make them either more reliable or scalable.  What important things about architecture and frameworks should developers know before designing a website and what are some architectural mistakes that developers should avoid?


I am not talking about the technical aspects as explained in [this post][1], but rather architectural aspects such as clusters, message queues, frameworks, data partitioning, batch processing, etc.. What are the best practices for using such components and how should they be put togeteher to produce reliable, scalable and dependable websites?  


  [1]: http://stackoverflow.com/questions/72394/what-should-a-developer-know-before-building-a-public-web-site