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.'"

Comments

Re:No longer possible

[nighty5]

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.

Query Types

[PhYrE2k2]

Have you actually performed side-by-side comparisons using your own data?

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