All the server technologies that you list are “sufficient” for the amount of traffic that you expect if you design your site well in terms of performance and scalability — and therefore many others that you have not mentioned, such as other approaches based on Java, C #, and (last but not least) Ruby (possibly with Rails, although, like other languages, you have several frameworks for you).
Like everyone else, client-side considerations are clearer - if you don't want to try a “server-side code generator on the client”, for example gwt (I was told that the latter works well, but I personally always fear code generators, for example, using a code generator without understanding the "code" that it does for you, that in this case it is HTML, CSS and Javascript with its own structure). With the exception of GWT and similar approaches (if this is your chosen poison), really learning HTML, CSS and Javascript is really a must - and then again you can choose from many, many frameworks (jQuery, Dojo, closure , etc., etc.) d.).
For performance problems, you really want to study the site (and books, etc.) Steve Souders - Steve was the server guru until the measurement showed him that the bottleneck was really on the client side and then it turned into a wizard on the client side ;-). But to get the most out of books, you need an understanding of HTTP, HTML, etc. Etc., To start with :-).
Alex martelli
source share