Comment Re:10:1... Really? (Score 1) 752
like you're stating, sometimes it truly is the best solution to have multiple technologies in place, as long as they're smartly used. If not, you end up with a maintenance nightmare.
Amazon.com is a great success story and an example of using different technologies well, and it came about because they got their architecture correct. It started as a single C++ app talking to a backend, and that wasn't really going to scale well. I've heard that a single page on Amazong.com might talk to 100+ different services. In some places they use java servlets, in others they use Perl/Mason.
I've seen smaller companies with hybrid systems due to evolution or the top-down "we need to recode this but don't have a full budget." They tend to have real problems and the technology drags down the rest of the business. In a team of 5 people, it's hard to hire when you have 2-3 different technologies. When you're larger that's less of an issue, as you can have people devoted to an area of your software pile that is in the language or set of technologies they are good at.