Karl Seguin’s got a post on a topic near and dear to my heart - MySQL on Windows. We’re running ASP.NET with a MySQL back end, which happens to be the same kind of setup that he’s looking at for an upcoming project. When we made the decision, it was the early days in the company and we couldn’t afford SQL Server licenses but needed to support some legacy ASP code, so we were driven by necessity. Karl actually took some basic metrics, so, uh, good for him.
Shortening his short version of the story, InnoDB on 5.x might be problematic, but ASP.NET connects at about the same speed as PHP does, and MySQL on Linux blew away SQL Server on Windows. It was a simple test that shouldn’t provide any real conclusions, but hey, it gives me a much stronger position than “uh, we run it because we had to.”
For the record, I love the MySQL/ASP.NET combo, at least if you’re tied to IIS like we are. For code, while we do have some PHP applications, I’m quicker and more comfortable (and thus more productive) with C#. For the db, there are a lot more web developers out there running MySQL and posting stuff online about it, so I’ve got a broader knowledge base to draw from when I have a riddle to solve.
Post a Comment