Apache, MySQL, and .Net - The Adventure Continues
-
John Simmons / outlaw programmer wrote:
The benefit of running Apache instead of IIS is that when I do move back to an earlier (non-server) version of Windows, I don't have to start from scratch with an older version of IIS and worry about having to do stuff different ways.
OK, that makes sense.
John Simmons / outlaw programmer wrote:
Actually, MySQl is equally as viable as SQL Server. Besides, now I can use either one, where you're stuck with just SQL Server.
At my previous job (until a couple of weeks ago) I was using MySQL from C++ on Linux. It is OK for light loads and small databases, but when things grow a little bit, better stay away from MySQL.
Nemanja Trifunovic wrote:
It is OK for light loads and small databases
AFAIK you are right that in a one to one comparison SQL Server will beat MySQL. SQL Server will ultimately hold more data and respond better. As a monolithic RDBMS interface SQL Server > MySQL. But as soon as you compare a real world situation with multiple servers, application layers, caching systems, sharding etc. then I think MySQL has been proven to work very well and at lesser cost (not free) than SQL Server. The platform support is also better. Google is also having good success with the open nature of MySQL and being able to patch problems they come across. If they find a problem they don't have to seek permission, engage with Microsoft engineers, check their license or wait for updates, they just fix the problem.
regards, Paul Watson Ireland & South Africa
Fernando A. Gomez F. wrote:
At least he achieved immortality for a few years.
-
John Simmons / outlaw programmer wrote:
The benefit of running Apache instead of IIS is that when I do move back to an earlier (non-server) version of Windows, I don't have to start from scratch with an older version of IIS and worry about having to do stuff different ways.
OK, that makes sense.
John Simmons / outlaw programmer wrote:
Actually, MySQl is equally as viable as SQL Server. Besides, now I can use either one, where you're stuck with just SQL Server.
At my previous job (until a couple of weeks ago) I was using MySQL from C++ on Linux. It is OK for light loads and small databases, but when things grow a little bit, better stay away from MySQL.
Nemanja Trifunovic wrote:
At my previous job (until a couple of weeks ago) I was using MySQL from C++ on Linux. It is OK for light loads and small databases, but when things grow a little bit, better stay away from MySQL.
You are joking right? I must have missed the smiley. MySQL excels at read often, write seldom databases. There are many large databases with huge loads running MySQL. I guess that's why Sun bought them.
-
Nemanja Trifunovic wrote:
It is OK for light loads and small databases, but when things grow a little bit, better stay away from MySQL.
Companies using MySql : Wikipidia Nokia Youtube NetQos flicker its is said that google also runs MySql (unconfirmed)
Artificial Intelligence is no match for Natural Stupidity
No one can understand the truth until he drinks of coffee's frothy goodness. ~Sheik Abd-al-Kadir
I can't always be wrong ... or can I? -
Shog9 wrote:
If your web host allows you to install them, or you self-host.
It was my impression that John was self-hosting? :~
I am.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001 -
For 1, I would say bad experiences with IIS (at least prior to the newer versions). For 2, I have no idea, other than cost :)
¡El diablo está en mis pantalones! ¡Mire, mire! Real Mentats use only 100% pure, unfooled around with Sapho Juice(tm)! SELECT * FROM User WHERE Clue > 0 0 rows returned Save an Orange - Use the VCF! VCF Blog
-
John Simmons / outlaw programmer wrote:
The benefit of running Apache instead of IIS is that when I do move back to an earlier (non-server) version of Windows, I don't have to start from scratch with an older version of IIS and worry about having to do stuff different ways.
OK, that makes sense.
John Simmons / outlaw programmer wrote:
Actually, MySQl is equally as viable as SQL Server. Besides, now I can use either one, where you're stuck with just SQL Server.
At my previous job (until a couple of weeks ago) I was using MySQL from C++ on Linux. It is OK for light loads and small databases, but when things grow a little bit, better stay away from MySQL.
http://www.mysql.com/why-mysql/case-studies/[^] If you look down the page of case studies you'll see: "Utel handles 10,000 Requests per Second Using a Scale out Deployment of MySQL Network" Not a bad scale out in my opinion. Are you sure you researched this topic enough to flame the product? Maybe you didn't optimize your db or something.
-
i thought mono was only for Linux installations. John's running Windows.
-
i thought mono was only for Linux installations. John's running Windows.
It's OSS, you can probably find a distro that'll run on your digital watch. :rolleyes:
Otherwise [Microsoft is] toast in the long term no matter how much money they've got. They would be already if the Linux community didn't have it's head so firmly up it's own command line buffer that it looks like taking 15 years to find the desktop. -- Matthew Faithfull
-
It's OSS, you can probably find a distro that'll run on your digital watch. :rolleyes:
Otherwise [Microsoft is] toast in the long term no matter how much money they've got. They would be already if the Linux community didn't have it's head so firmly up it's own command line buffer that it looks like taking 15 years to find the desktop. -- Matthew Faithfull
Yeah I just looked on the mono-project.com site and there is a windows install of it. If you want cross compatibility you program for Mono and it "should" run on both platforms. It will be interesting if commercial packages convert their code to support Mono or not.
-
Well, after a couple of weeks (four full days and only an hour a night on week days) of developing a website, integrating a MySQL membership/role/profile provider, and implementing Forms Authentication, I copied the whole shebang to the (windows 2003) server running Apache 2.0.55, and waddayaknow - it bloody well worked! I think this whole experiment can be marked down as a resounding success, so if you've been holding back on running Asp.Net 2.0 under Apache, or using MySQL with .Net, there's no real reason you shouldn't be able to proceed.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001Nice to about unexpected success. Caused an interesting thread, too. Most of the time I hear about unexpected failures (bugs). This is like a juicy raisin in the muesli - a surprisingly rare sweet moment of positivity that doesn't turn out to be artificial on closer inspection. I once built a simple website using VS2005 and was pleasantly surprised at how well it worked with the major browsers on my friends' PC's. In fact I could hardly believe it. I cling to stuff like that at times of deep MSdespair.
I'm peculiar to myself, therefore I am.