4 ms·
Is it really fair to take a cursory look at someone's architecture and call them out like that? It's especially unfair to throw out something like "I've had a s
by bradleyland 14y ago
Is it really fair to take a cursory look at someone's architecture and call them out like that? It's especially unfair to throw out something like "I've had a sustained 4k-5k on a single un-optimised instance of nginx." Serving what? Is your problem in any way similar to theirs? Do you have a full understanding of their problem?
- eropple 14y agoI used to work at TripAdvisor, and I don't think he's wrong. TA is a fun company with a lot of really sharp engineers on the payroll--it was a privilege to work with the folks I worked with. But the business focus is on time-to-market, and 10+ years of that can lead to technical debt, which can often present in ways like "requires enough AWS instances to calculate every digit of pi to not fall over." That focus is a conscious decision on their part, though, and their success speaks for itself.
- bradleyland 14y agoI'm not saying he's wrong about their efficiency. I'm saying it sucks to come behind someone and make blanket statements about their efficiency of utilization without knowing any details. If you worked there, you're in a much better place to comment.
- deleted 14y ago[deleted]