StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>Amazon EC2 works well, but don't base your pricing on the $0.10 instances -- they are very underpowered. I recommend starting with at least c1.mediums. I like to use nginx instances as load balances on m1.small's infront of c1.medium web server instances (all the apps I've built recently are CPU bound and not memory bound).</p> <p>3 seconds is a long time. I typically use 200ms-400ms for a performance objective. Of course this changes depending on how time sensitive your app is and how much work has to be done.</p> <p>If there's really 3 seconds of work to be done, you can probably have a backend grid pre-processing data. You then probably need fewer web servers since they are mostly returning premade data.</p> <p>If I were in your shoes, I'd build a prototype in whatever language/platform I'm most comfortable in. Then you can get an idea of where you'll need to take it.</p> <p>Don't forget that it takes time to build a high performance web app. You need to code, benchmark, repeat to scale and get your response time down.</p> <p>The number of instances in which you need to write your own webserver are very slim. This is not one of them. There are many to choose from. Assuming a nix based platform, you can use Apache, nginx or lighttpd. There's a bunch of other ones, but they are typically used as app servers (tomcat, zope, mongrel, etc) and have apache/nginx/lighttpd/squid proxy in front of them.</p> <p>I haven't really used an off the shelf platform (solution) for building web apps (I'm assuming you mean some sort of java stack or .Net stack). I can't really help you there. Most of the tools I work with (LAMP type stuff) are componentized and allow drop in replacements at every piece of the stack. It's not uncommon to outgrow one component and have to replace it with another. </p> <p>For example, no load balancer -> software load balancer -> software load balancer capable of buffering -> hardware load balancer. All of these are cost effective for different levels of scale. </p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

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