The relational DBMS industry is filled with startups. In some way or other, most of them are based on or make use of the open source project PostgreSQL. (Not all, of course; exceptions include DATAllegro and Infobright, which are based on Ingres and MySQL respectively.) But how they use PostgreSQL varies greatly.
EnterpriseDB is at one extreme. It hired a number of the top PostgreSQL developers, and is widely credited in the industry for major enhancements in PostgreSQL 8.3. Look in the future for EnterpriseDB to be less “The Oracle-compatible database company” and more “The PostgreSQL company that offers great features, including Oracle compatibility.”
Vertica is at the other pole. I still have the impression that Vertica emulates PostgreSQL to gain various tool compatibility benefits. But upon checking I learned, to my surprise, that Vertica uses no actual PostgreSQL code whatsoever.
Greenplum is somewhere in between. Greenplum started from PostgreSQL, and said it was supporting something open source called Bizgres. But Seth Grimes calls Greenplum’s commitment to Bizgres into serious question. But then, given how silent Greenplum has been recently (some PR around an investment round excepted), I’m not sure what to think of anything I previously heard from the company.
Please subscribe to our feed!
Database
MySQL
management
systems
relational
--vertica
--enterprisedb
This is the second of a five-part series on database management system choices. For the first post in the series, please click here.
For the most part, relational database management systems divide into four major classes:
High-end OLTP relational database management systems are complex and mature products, differentiated mainly on reliability, availability, performance, scalability, security, license cost, maintenance cost, programming/administration cost, and datatype support. All except the last point can be evaluated pretty effectively on an outside-in basis. That is, is suffices to look at proven results, without worrying a whole lot about architecture or product futures. Just remember that a lot of the high-end features come through extra-cost add-ins, which need to be included in any evaluation.
That said — most evaluations of high-end OLTP RDBMS are pretty moot anyway. Large enterprises usually have one favored vendor, who provides a significant quantity discount on license and maintenance costs. Using the OLTP RDBMS you already have also usually leads to significant efficiencies in administration expense. Thus, the high-end OLTP is the one part of the DBMS market that truly is as mature as conventional wisdom would have us believe ? at least, that is, until something like H-Store comes to fruition.
Even so, high-end relational OLTP DBMS vendors face two major competitive challenges, which are taking significant share of new applications within those vendors’ installed bases. For more about those, please see the next two posts in this series.
The complete series
Please subscribe to our feed!
More from me soon, but first here is a survey of what other people are saying about Sun’s billion-dollar deal to acquire MySQL:
In the past, when I’ve asked Jeff Jones of IBM for permission to post one of his well-written notes, his response has pretty much been “Of course! Why did you bother asking?” So this time I’m just going ahead and skipping that step. The note is about IBM’s mid-range flavor of DB2, targeted directly at MySQL.
Today, IBM announced that its popular DB2 9 Express-C software is now available with an optional low-cost yearly support subscription. DB2 Express-C has been available without license charges for downloading, application development, deployment and redistribution since January 2006. It remains available without license charges for those that do not require support. Electronic general availability of the new support option is scheduled for June 1, 2007.
The new DB2 Express-C support option provides 24×7 product support, regular fixpacks and upgrade protection. In addition, this option provides support for high availability clustering, offsite disaster recovery, and data replication with remote data servers without additional charge.
Background
– Subscriptions are priced at $2,995 (U.S.) per server per year. This is identical to MySQL Enterprise Gold, but DB2 Express-C includes features not found in MySQL including pureXML support, high availability clustering (MySQL Cluster support costs extra), autonomic features, and no-charge administration and development tools. Unlike the free offerings from Microsoft and Oracle, DB2 Express-C does not place limits on the size or number of databases managed. With up to 4 GB of memory and up to 2 processors, DB2 Express-C can run on more powerful servers, can scale higher and can perform faster than its competitors.
At noon Eastern Time on Wednesday, April 25, I?ll be doing a webinar about midrange OLTP/multipurpose DBMS, sponsored by EnterpriseDB, who not coincidentally are purveyors of same. You can sign up here.
Below is some of EnterpriseDB?s verbiage promoting the event. I particularly like the part where they refer to me as a ?renowned industry guru.?
The DBMS market, once thought to be an oligopoly, is experiencing some refreshing disruption - thanks to open source-based databases that are proving viable alternatives to traditional, more costly incumbents. Whether you’re trying to control database costs or support new application development, there’s never been a better time to reevaluate your database platform strategy.
But, how can you realistically compare alternatives like MySQL and EnterpriseDB against established database platforms like Oracle, DB2, and SQL Server?
Let your applications be your guide.
In this webcast, renowned industry guru Curt Monash provides an objective context in which to evaluate and select the right DBMS based on your application’s needs. He’ll discuss how all DBMS’ features are not all created equal in the way they address application-specific demands. Particular focus will be given to the unique requirements of transaction-intensive applications.
Join us for this eSeminar and learn how to:
- Go beyond the typical feature checklists of self-proclaimed “enterprise-class” offerings to provide a more in-depth barometer of a DBMS’ true capabilities
- Define the DBMS platform requirements for a variety of transaction-intensive applications
- Delineate between must-have and nice-to-have DBMS features for your application
MySQL told Computer Business Review they’re thinking strongly of an IPO this year, but also wouldn’t mind waiting. Frankly, I think they shouldn’t come public until they can prove solid acceptance of Version 5, because Version 4 remains in too many ways an embarrassment.
Also, investors need a chance to see whether MySQL’s new enterprise all-you-can-eat pricing scheme is a success, both financially and in terms of service delivery.
Database
theory
relational
practice
&
technology
source
and
MySQL
vendors
MySQL
vendors
appliances
warehouse
relational
db2
&
technology
and
--Oracle
Data
--Open
vendors
relational
&
technology
source
RDBMS
MySQL
----MySQL
Data
MySQL
source
technology
&
relational
vendors--Open
RDBMS----MySQLMemory-centric
mgt.
Data
MySQL
source
technology
&
relational
vendors--Open
RDBMS----MySQLMemory-centric
mgt.