IBM Sets DB2 Database Free (Beer)
Anonymous Coward writes to tell us that in the hopes of winning more developer interest, IBM has released a free version of their DB2 database. From the article: "DB Express-C is the same database as IBM's commercial offerings but the company places limits on what kind of hardware it can run on. It can be deployed on systems with two processor cores or up to two dual-core chips on Advanced Micro Devices- or Intel-based servers. The memory limit is 4GB but there are no limits on the size of database or number of users. "
I'm glad you're happy with MySQL for your personal web site. But what does that have to do with DB2? IBM is trying to attract developers, not small web site webmasters.
"Who are in control, they are not in control of anything - they don't even control themselves!" - Glen Beck
"Migrate Now! for DB2 Universal Database (UDB) facilitates the migration from Oracle, Sybase, Microsoft SQL server, and additional database platforms to DB2 UDB at a special price. Migrate Now! is an end-to-end offering that includes migration tool kits, no-charge online education, sales teams and resources to assist you in planning and implementing your migration based on IBM's proven methodology."
I think it falls directly in step with IBM's shift in strategy - lower the software cost and generate service based revenues. I don't think I'll be moving my stuff over anytime soon. Oracle on the data warehouse (the app was built before mysql could do cross table updates), mysql on the select only local repository.
IBM may be too late for the vast majority of developers. The ones that offered their products to develop and learn on are the ones that will find some sort of loyalty.
I'm glad you brought up performance versus scalability. PostgreSQL is often considered slow by MySQL fans who fail to understand the concept of scalability. Simply stated, MySQL is typically faster than PostgreSQL with low scalability requirements yet PostgreSQL tends to scale much, much better than does MySQL for both complex queries and highly concurrent, mixed operation loads. Obviously, this is a rule of thumb and not a hard/fast rule. I'm sure there are corner cases (which is often put forward in MySQL benchmarks, which are not reflective of real world applications) in each camp which ignore the rule.
For people that do not understand scalability versus performance, let's put it like this:
MySQL is fast for one user and PostgreSQL, while fast for one user, tends to be slightly slower than MySQL. On the other hand, add a hundred concurrent, mixed operation (aka, not read only) users and MySQL tends to go belly up. At the same time, given the same example, PostgreSQL is happily chugging along; albiet at increased latencies. Of course, this statement is broad and makes many assumptions, but it will hopefully help others understand the concept.
So, given your rankings above, PostgreSQL, tends to find a middle ground between Oracle's performance/scalability ranking. In other words, PostgreSQL tends to scale less than Oracle yet tends to perform better. MySQL, on the other hand, performs fairly fast for read-only databases but scales very poorly.