Quote from: gweedo on April 07, 2013, 07:02:51 PM

Quote from: Capitan on April 07, 2013, 06:52:36 PM

Quote from: gweedo on January 27, 2013, 04:11:28 AM

Quote from: schalk on January 27, 2013, 04:04:04 AM

What point are you trying to get a across? That to optimise a website you need System Engineers? Well that's kind of a given when you are looking at a scale that big.

You will have these exact same problems with MySQL when looking at that scale. You can only scale up to some extent, then you will require techniques to allow you to scale out, like using replication.

If you read the article and look at how there setup is, they obviously are locked into a scenario where they can't even change databases, so the only way they can scale is with hardware. Now you can get more performance out of MySQL but either changing the database engine, or even using a mysql build that has beter performance and is tested. Kinda like twitter. SO the point I am trying to get across is that with ASP.NET and C# the only way to scale is thru hardware, and with other options you can just switch out some software and then you can do hardware scaling. So yea what would you want to do spend cash as a startup on hardware? Or go with this proven software that is free?

I am a professional developer. I currently work in Python, but have worked in Ruby, Java, and also have years of experience with .NET. I just wanted to let anyone who is reading this that gweedo flat out doesn't know what he is talking about.

1. Stackoverflow chose to have a scale up architecture. I am skeptical that this would be a good choice for most businesses, and am waiting to see if eventually their gamble will fail. They essentially have bet that their traffic will not grow faster than hardware can. So far that has proved to be true. This has nothing to do with choosing .NET, and more to do with choosing a scale up approach for their database.

They would have the same exact problem if they tried with MySQL, and MSSQL is more proven when it comes to high performance at scales that large (even when you "just swap out some software" as you put it, which by that I assume you mean optimize which storage engine you're using, but that alone still won't let MySQL scale UP better than pgSQL or MSSQL).

2. This has nothing to do with their choice of using .NET. They are using SQL Server as their database. Yes, .NET tends to go hand in hand with SQL server but there is no reason that has to be so. There are lots of projects that use .NET with an open source database like pgSQL or MySQL.

3. .NET is a compiled language, and statically typed. The compilers are very sophisticated, and the language features are very advanced. .NET actually tends to scale and perform better than dynamic languages like Ruby, PHP, and Python.

The scary part about the internet is it lets people who have no idea what they are talking about propagate bad information. I'm sure gweedo means well but his posts in this thread as uninformed. This is how .NET gets such a bad rap. I think all languages are suitable for mos tasks. I stay away from Ruby because it's become the language where all beginners flock to, and they seem to have a lot of security flaws lately. Python and .NET are my two goto languages now. As long as you have developers who know what they are doing, they can make any project work and scale in their language of choice. So most language vs language arguments are stupid to begin with, but they are still full of people spouting off incorrect information.

First off, thanks for bumping a thread that was dead a long time ago. Obvious you didn't read any of my post but one and decided to comment on that.

Did do any research do you have any information that would prove these points? I at least pointed to an article that proved what I was saying, yet that isn't the post you quoted. Obviously your the misinformed one.

Which points specifically do you want me to prove? Any developer who understands scaling a database driven app would understand the concept in #1. It's called scaling up vs scaling out. I'm not going to dig up links for you, feel free to google it yourself.

#2 is also a fact. .NET is not a database, it is a software platform. You can access any database from .NET apps, including MongoDB, Cassandra, MySQL, MariaDB, PostGresQL, etc. Again, feel free to find links that disprove this. Just search for any of those db names + "C# driver" or "C# client" and you'll find the drivers for connecting to those db's.

#3 is also well understood in the programming community. It's well known that statically typed, compiled languages tend to be faster than dynamic ones. That doesn't make them better than dynamic ones. In fact, people often argue that the increased productivity and flexibility of using dynamic languages like python and ruby outweigh the benefits of typed/compiled ones. See any discussion about javascript and typescript, C# vs Ruby, C# vs PHP.

I'm presenting some alternate viewpoints for you here. It's up to you if you want to stick with the uninformed ones you are holding or if you want to look into what I'm trying to clue you in on. I'm definitely not saying .NET is better than any other language. I think those types of statements are stupid no matter what language they are for or against.