Oracle Acquires Sleepycat

Deven writes "Computerworld is reporting that Oracle has just acquired Sleepycat Software (makers of the open-source Berkeley DB embedded database) for an undisclosed sum. Having previously acquired Innobase, Oracle is certainly taking a look at diversity."

Comments

Interesting ....

[joe_n_bloe]

.. o O o ..

Can Oracle's acquisitions be predicted based upon the database backends used with MySQL? What other backends work with MySQL?

Re:Interesting ....

[jadavis]

How many of those engines are distributed under a free license and have transactional support? Looks like both are owned by Oracle now. Oracle did that for a reason, and it's not because they like to collect database companies.

Many users of MySQL depend on one or more of:
(1) the ability to license MySQL commercially with one of those engines cheaply
(2) the continued development of those storage engines
(3) the continued development of MySQL

Oracle can now stronly influence all of those things. #1 they can just raise the price or not license. #2 they can just lay off all the developers. Good luck getting an open sources devel team together before it's too late. #3, they can just refuse to license those backends, thereby preventing #1, which is also MySQL's source of revenue, leading indirectly to exactly the same case as #2.

Taking a look at Diversity?

[hedronist]

Diversity? It looks more like careening towards homogeneity to me. First they bought Innobase, giving them the ability to cut MySQL's transaction nuts off, then they buy another open-sourece-friendly DBMS which has transaction capability.

Now, if you were the largest commercial DBMS vendor in the world and you were worried about the OSS people moving into your space, what would you buy in order to stop them cold? Me? I'd keep them out of atomic transaction space.

Do keep in mind we are talking about Larry Ellison here. Just google on "larry ellison greed" to see what some other people think of this champion of diversity.

Two MySQL backends owned by Oracle

[jadavis]

Oracle now owns two MySQL backend products. First InnoDB, which was their primary transaction-supporting backend, and now BerkeleyDB. Now, in order for MySQL AB to license MySQL database commercially, they need Oracle's permission (that is, if they want basic database features like atomic transactions).

And if you don't get a commercial license from MySQL AB, you can't link the mysql client library to a non-GPL application. That means, if you have a non-GPL application and you want to add support for MySQL, you are now dependent on Oracle.

Chump change to Oracle

[jonsmirl]

The price of these acquisitions is chump change for Oracle. My bet is that they are buying these companies to destroy them. Oracle does not want something like Mysql becoming a real threat to their DB business, so the tried and true solution is to kill the babies before they grow up. They will attempt to migrate what customers they can and then stop development on the acquired code bases. The acquired developers, if they stick around, will be put to work building migration tools.

Challenge for Open Source

[cyberjessy]

This could become one of the biggest challenges for Open Source in the years to come. The biggies could but these companies (often run by a handful of good men) for a small sum; and then change the way they function. Of course the old source will still be available, but the guys who know the intricacies will no longer be working on it. Bug fixes might be late, new features may never come. Many of the old users will leave, some stay hoping for the best. All the roadmaps vanish. Until someone picks up the ashes and starts again. Rebirth.

I am not sure how fair it will be to ask any company/people to not take a multi-MILLION dollar offer, so that they would remain FREE.

You can mod this funny, 'cause after I finished writing it feels like a para from MadMax.

Re:Its not competition - Oh yes it is

[Snowhare]

Do a Google groupd search for MySQL. Do a second one for Oracle.

Surprise! MySQL has 75% as many messages about it as Oracle does.

They damn well are competition. They are eating Oracle's entry market. Not everyone needs a super-duper database. A good enough free database trumps a extremely overpriced 'perfect' one in most applications.

Sleepycat responds

[Chairman]

I'm Mike Olson, Sleepycat's (now former!) CEO. I've taken a job as VP at Oracle working on embedded databases. Our entire team has come along.

I've posted a summary of this announcement on the Sleepycat blog, at http://blog.sleepycat.com/2006/02/next-ten-years.h tml. I understand that a big vendor making a series of acquisitions in open source causes concern, but I'm convinced that the plan is as outlined in my posting. We're all showing up for work every day and working on the same embeddable database technology as ever. We're continuing to close deals with new customers and to support old ones. We continue to work closely with open source users.

There's lots of speculation that this move is intended to damage MySQL. I frankly don't see it; MySQL doesn't depend on Berkeley DB. It never did. We've always had a close and cordial relationship with those guys, but both businesses have always concentrated on our own customers and markets. We may have wished, sometimes, that we collaborated more closely, but we never did.

We've been good members of the open source community for a long, long time. We're pleased our software is so broadly used, and we're proud of the projects that rely on it. While I understand the concern, here, I'd ask that you watch what we do. I'm confident in the future of our products and of open source. Give us time to show you what Oracle and Sleepycat can do together.

Re:Sleepycat responds

[hypersql]

I don't agree MySQL does not depend on Berkeley DB. Without it, and without InnoDB, MySQL needs an alternative. In any case it's bad for MySQL, because some customers are probably already scared.

I think what Oracle will do is change the work priorities inside Sleepycat. Development and support related to MySQL will be stopped completely. Developers will be re-assigned to do things like 'compatibility', 'migration' and so on. Future version of Sleepycat will just not work with MySQL any more. Probably the license agreement will change. Not sure if the code will be forked, but if the main developers of the codebase are gone (no longer working on it), the code becomes a legacy.

Something very similar happened to me in 2001. I am the original author of Hypersonic SQL (a Java database engine). PointBase, who also developed a Java SQL database, asked me if I want to work for them, I said yes. We agreed I will continue to work on Hypersonic SQL. But this suddenly changed about half a year later, and they made me to work on something else (PointBase Micro, PointBase UniSync). So they 'bought' me (well, I only got shares, which are now worthless). And then tried to kill the competitor. They told me to stop the Hypersonic SQL project. But it was forked (HSQLDB). I left PointBase in 2003, and now I'm working on a new Java database: H2 (http://www.h2database.com/).

MySQL will probably start developing their own transactional backend. They have now enough money to do that. They should do that, probably they already started (I was asked to work for them, but obviously I said no because of H2). My guess is MySQL will start a branch in the Bay Area, and hire some good developers there. There are quite a lot good database developers in this region.

Thomas Mueller, former author of Hypersonic SQL