Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>This space is changing very quickly right now so I think you will find a lot of different good answers. If I where to do something on the cheap right now I would probably pick the following stack:</p> <ul> <li>Web server: apache</li> <li>App server: tomcat - use the <a href="http://tomcat.apache.org/tomcat-5.5-doc/cluster-howto.html" rel="nofollow noreferrer">clustering support</a> if you need to grow or split at the <a href="http://httpd.apache.org/docs/2.2/mod/mod_proxy_balancer.html" rel="nofollow noreferrer">apache level</a> or even introduce a <a href="http://www.apsis.ch/pound/" rel="nofollow noreferrer">load balancer</a> box at the very front</li> <li>DB server: MySql - mainly because it is easy to cluster</li> <li>Platform: <a href="http://scalr.net" rel="nofollow noreferrer">scalr</a> - The cloud setup is simple and cheap. It uses <a href="http://aws.amazon.com/" rel="nofollow noreferrer">Amazon's cloud</a> on the backend and that gets you a lot of extras like putting servers in different datacenters for redundancy.</li> </ul> <p>Now you can add in or remove parts of this. You may not need a web tier out there and can just expose tomcat directly. You may need EJBs and in that case you can just fire up more nodes for that and create another tier. You may want to add a tier for load balancing in front of apache. You may want to use the <a href="http://aws.amazon.com/cloudfront/" rel="nofollow noreferrer">Amazon cloudfront</a> service to push static files to their edge network.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload