5 ms·
This points me to the exact opposite conclusion. Why wouldn't I want to write my webapp in an efficient language and framework? If a tiny bit of extra effort me
by saosebastiao 12y ago
This points me to the exact opposite conclusion. Why wouldn't I want to write my webapp in an efficient language and framework? If a tiny bit of extra effort means I can keep my app on a single EC2/RDS pair for a long enough to last until my first hire, I think that's worth it. It means I don't have to worry about setting up and tuning and maintaining load balancers, memcached servers, etc. Sysadmin/Devops work is a large enough distraction from the product that I would prefer not to have it at all. Efficient software frameworks/languages give me the breathing room I need to focus on the product.
- stouset 12y agoAny choice of language is going to satisfy your requirement of one app server prior to your first hire (for most everything not involving huge amounts of data processing). If your code performs poorly enough that this isn't the case, the problem isn't the language — it's you, and no language would have saved you. That said, there are so many benefits of running multiple servers behind a firewall off the bat, I can't fathom why people don't do this. It more or less enables trivial failover for many classes of problem, and deploys are no longer as large a source of instability: deploy by launching a new box, route a small amount of traffic to it at first, then route all of it. If there's an issue, route to the previous app servers. Compared to the time wasted by getting the architecture wrong off the bat (and months of pain while you wait for there to be enough time to do the work, which never happens), this is a massive win.