Slashdot Mirror
MySQL To Be Ikea Of The Database Market
Rob wrote to mention an article discussing MySQL's intent to become 'the Ikea of databases'. From the piece: "While new entrants into the open source database market, such as EnterpriseDB and Pervasive Software, have made no secret of their intentions to chase Oracle's market share, Mr Mickos said MySQL is happy to leave them to it. 'We are thankful that they are there to define the market, there is no product if you're the only vendor,' he said. "Pervasive and EnterpriseDB are going up against Oracle. We don't want to be in that space, we don't want to take the heat from Oracle. If you're working in a zoo you don't want to be the one who has to brush the teeth of the lion.'"
That every installation comes with an Allen key and crappy instructions?
Pervasive and EnterpriseDB are going up against Oracle. We don't want to be in that space, we don't want to take the heat from Oracle. If you're working in a zoo you don't want to be the one who has to brush the teeth of the lion.
That should nip the "MySQL is a replacement for Oracle under all circumstances" posts that always appear whenever MySQL is discussed on slashdot. It should, but it won't.
OIn a different note, isn't the "Ikea of databases" space already a little overcrowded? There's Firebird, McKoi, One$DB/Daffodil DB, Cloudscape, Postgres etc. Guess MySQL already pretty much own that space, so this is just a reaffirmation that they're sticking to their knitting. Doing what they do best. Very wise.
Yes, Windows brought MySQL to me.
I host my site on a commercial service, and previously I was stuck with using Access as my DB, unless I wanted to pay big SQL Server bucks. My site crashed 5 or 6 times a day because of the load on the database.
Finally my hosting service started to offer MySQL, for free...
My site stopped crashing, and now everything loads a lot faster. (I haven't converted the entire thing over to MySQL, but enough to stop the crashing.)
If MySQL were not free, I would not have converted. If it were not on Windows, I would not have converted.
But now I see it as a real possibility for use at work.
No reason to lie.
...you can take it home without a big transport, you have to figure out what they mean by odd instructions and you have to perform the assembly yourself, but when you are done you can save a bundle if your time is not that valuable.
Since when are stored procedures, triggers, and views (freaking VIEWS) enterprise features? Log shipping or automatic failover are enterprise features. Procs and views are basics.
Unlike Nintendo, I think the MySQL people have a point though. You wouldn't want a $100k Oracle DB for a website that can be handled by $5k of white boxes running MySQL, just like you probably wouldn't expect a stuck-up billion dollar business to use an open source DB.
I would search through benchmarks and wonder, "What kind of database defines me as a person?" We used to read pornography. Now it was debug prints. I had it all. Even the opteron optimized version that can take over 2Gb / process, but it still maxes at 4Gb due to 32bit pointers - proof it were crafted by the honest, simple, hard-working indigenous peoples of wherever. I am Jack's wasted memory.
And how can I deck out my house in mid-century modern MySQL? I'd like to see that.
There's a large supply of tables to choose from. You even put them together yourself. Just name them Coffee, Kitchen, End, etc.
Why all these crappy slashdot posts about MySQL we have been seen lately? They speak as if MySQL where an uncontested champion in the free-software database arena. This is far from true. Many articles doesn't even mention PostreSQL. Many of them says "Now MySQL is a big player because it's got... transactions" (!).
I think there's interest here in building up the idea that MySQL is important. There's currently no reason to use MySQL, because other products already do what it does and better.
Have you actually performed side-by-side comparisons using your own data? I have on many projects. Some are faster in Postgres. Some are faster in MySQL. Guess which one I use? Both. I use Postgres when it is faster. I use MySQL when it is faster. I refuse to be a blind moron like so many on Slashdot: Postgres is best. No, MySQL is best. Who cares - does it run Linux? No, Debian. That is Linux. I use BSD! Who cares, we're here to bash Windows!!!
The previous comment is purposely vague and generalized, but all of the facts are completely true.
If you're happy with MySQL than great.
Its offered at most ASP's for next to nothing.
But just to let you know PostgreSQL 8.x now offers a native build for Windows - and is extremely powerful.
Bingo. I couldn't agree with you more. MySQL is fairly lightweight, easy to use for many newbies, and provides some pretty advanced features for most tasks. It has its quirks to be careful of, but ultimately does its job as a DBMS. MySQL is extremely quick on the read, but suffers from locking issues and concurrency issues on the write. So it's fantastic for the Web- which is why you see it so often on hosting providers and other similar providers- it's quick to put Web content into. It's quick to hold userIDs/passwords that aren't updated frequently. It's quick in anything where reads are heavy and writes are sparse. Service providers like it because it's not too resource intensive for read-heavy uses (web sites) and it has a great user model (store users in a database, provide per-database permissions and hide all other customers from seeing other people's databases) for many-user systems.
PostgreSQL does a fantastic job with sites needing more complexity. If you need to start with transactions, need good read/write performance, and feel that data integrity is key (generally things dealing with dollars, accounting systems, online applications, booking systems, etc) then of course the way to go really is PostgreSQL if supported. If it's not (as it is with many hosts), there's always some MySQL transactional support with row-level locking, but it almost seems like a hack. (as a note, PGSQL8.1Beta2 provides support for 'roles', but to my knowledge still doesn't hide other people's databases).
Anyway- Each has it's ups and downs. Service providers love MySQL because it's fast, cheap, easy, and keeps users seperate. PostgreSQL I've seen abused a bit too much for things it's not to be used for, and that has a huge performance hit. Why the bickering? Everyone thinks their tool is bigger
-M
when you see the word 'Linux', drink!
- Schloönge
- Loob
- Vügeena
Ad nauseum...blog |