I'm interested in all startups using linux and windows environments. What do you use to scale to app to millions of hits per day ?
Ask HN: What technologies do you use in your startup?
1–10 of 24 posts
Re: Ask HN: What technologies do you use in your startup?
#2Rails, node.js, redis, resque, mysql, nginx, unicorn, monit, solr, ubuntu.
I don't think that the technology stack matters that much, though.
Re: Ask HN: What technologies do you use in your startup?
#3Scaling is more about sound architectural decisions than it is about stack.
(And it is more about "not a problem" than it is about architecture, because a gigantic proportion of all startups will never have any scaling problem to speak of, and the majority of the remainder will be able to solve theirs in fairly boring fashions.)
Almost all startups would be better served by playing around in their technology of choice looking for something that could possibly cause a scaling problem rather than planning for scaling problems.
Re: Ask HN: What technologies do you use in your startup?
#41. caching
2. prefer static content over dynamic, as much as possible
3. lots of machines, with the requests distributed across all of them
these 3 strategies alone will buy lots of scale
Re: Ask HN: What technologies do you use in your startup?
#5Rails, node.js, redis, resque, mysql, nginx, unicorn, monit, solr, ubuntu. I don't think that the technology stack matters that much, though.
while I agree that some of the strongest techniques for scaling are available on many platforms/stacks, you will generally have the easiest time of it on a Linux stack rather than say Windows. Only at the thousand-foot perspective does the stack not matter. But on the ground, where the devil is in the details, the stack matters quite a bit when it comes to what toys are available to you, what resources, what options.
Re: Ask HN: What technologies do you use in your startup?
#61. caching 2. prefer static content over dynamic, as much as possible 3. lots of machines, with the requests distributed across all of them these 3 strategies alone will buy lots of scale
That's the magic formula we use at work (200+ sites, many with 1 million+ unique visitors per month). I apply the same techniques to my own projects, even though it's unnecessary at this point.
Our sites run on a standard LAMP stack (load balanced across between 2 and 25 machines using an F5), memcached for object and query caching, caching at the application level, varnish and nginx for file caching, and limelight CDN for serving images, css, and javascript.
Re: Ask HN: What technologies do you use in your startup?
#7Rails, node.js, redis, resque, mysql, nginx, unicorn, monit, solr, ubuntu. I don't think that the technology stack matters that much, though.
while I agree that some of the strongest techniques for scaling are available on many platforms/stacks, you will generally have the easiest time of it on a Linux stack rather than say Windows. Only at the thousand-foot perspective does the stack not matter. But on the ground, where the devil is in the details, the stack matters quite a bit when it comes to what toys are available to you, what resources, what options.
I would say your familiarity with the stack you're using is what matters, both Linux and Microsoft platforms have been shown to handle massive loads with enough massaging.
I would also say it's a massive and on-going trial and error process to see what actually works, the biggest sites are still learning and falling over.
Re: Ask HN: What technologies do you use in your startup?
#8java (jee, spring, struts), hadoop, hbase, nginx, fedora, solr, activemq, ehcache/terracotta and a bunch of other OSS.
Re: Ask HN: What technologies do you use in your startup?
#9Rails, distributed erlang with a BERTRPC endpoint, memcache, redis, thin/sinatra/eventmachine. The key is the less work you have to do in the request response cycle and the more you can offload to better suited environments/servers, the easier time you will have adapting to new challenges.
Re: Ask HN: What technologies do you use in your startup?
#10Scaling is more about sound architectural decisions than it is about stack. (And it is more about "not a problem" than it is about architecture, because a gigantic proportion of all startups will never have any scaling problem to speak of, and the majority of the remainder will be able to solve theirs in fairly boring fashions.) Almost all startups would be better served by playing around in their technology of choic…
Engineers sometimes remind me of the two guys that used to live next to me that spent every day tinkering with the engine of their Camaro out in the garage. I'm sure it was pretty tricked out but it also spent 9/10 of its life up on blocks instead of actually driving somewhere interesting.