[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
|
|
Subscribe / Log in / New account

The launch of EnterpriseDB

May 25, 2005

This article was contributed by Joe 'Zonker' Brockmeier.

The EnterpriseDB Corporation announced the public beta release of its EnterpriseDB 2005 on May 23. The company has been in "stealth mode" for some time, and is just now coming out to launch the EnterpriseDB product.

EnterpriseDB is based on PostgreSQL 8.0.3, with modifications to make it more compatible with Oracle. The company's press release touts EnterpriseDB's open source roots, so we decided to get in touch with the company and find out what differentiates EnterpriseDB from PostgreSQL, what terms it is offered under and how EnterpriseDB works with the PostgreSQL project. In particular, we talked to the company's CEO Andy Astor. We also talked with PostgreSQL team member Josh Berkus about EnterpriseDB's involvement with the PostgreSQL project and the effect of increasing corporate attention on PostgreSQL in general.

What does EnterpriseDB add to PostgreSQL to make it interesting? Compatibility with enterprise databases, specifically Oracle, and a GUI Studio application.

The exact license for EnterpriseDB has yet to be determined. Note that the PostgreSQL project uses the BSD license and does not require that distributors make changes available. Astor confirmed that, despite the company's press release focusing on open source, EnterpriseDB itself will not be available under a license that would be OSI compatible.

Pricing is also up in the air. Astor couldn't give us specific pricing, but said that it would be "in the single thousand dollars" for a license. He did say that it would be free to download for testing, development and "low-volume usage" but that when used in "large-scale" environments that it would require a license from EnterpriseDB.

Astor told us that the company plans to contribute "everything we're building, after a fair amount of time... back to the open source community". Astor said that it's his belief that some development is best left to the open source community, in situations where there is "huge demand" and that "some things are best left to commercial interests". He also said that he expected that PostgreSQL would not adopt everything that the EnterpriseDB team offered. "I guarantee that the PostgreSQL community will not want to own all of what we've done". He did say that the final EnterpriseDB license would guarantee that users wouldn't be stranded if the company failed. "If the product we're selling is not supported by a commercial organization, it will be contributed to the community. That will be in every license that we sell."

The EnterpriseDB application will be available in binary-only form, and Astor said it would support "every 32-bit and 64-bit Intel-style platform". Right now, downloads are available for Fedora Core 3, SUSE Linux Enterprise Server 9, SUSE Linux Professional 9.2, Red Hat Enterprise Linux 4.0 and Microsoft Windows. Astor said that it would probably be available on Solaris, Mac OS X and other platforms "on customer demand". The EnterpriseDB site does require registration before download,

Since one of EnterpriseDB's selling points is Oracle compatibility, we asked Astor if it was fully Oracle compatible. Astor said that EnterpriseDB is not fully compatible, but "a large number of Oracle apps will run on us now, and that will increase as time goes by... not every aspect is supported, and we're looking for customer feedback". He declined to name specific applications written to use Oracle that were EnterpriseDB compatible, but said that "a lot of things we've been testing with run".

Some are concerned that this may be a dreaded fork of the PostgreSQL project. We asked Astor about compatibility with PostgreSQL going forward. Astor pointed out that the EnterpriseDB beta release was based on the current PostgreSQL release (8.0.3), and that EnterpriseDB is "fully compatible" with PostgreSQL. He also noted that the company was adept at keeping in sync with the PostgreSQL tree, and that the company intends to maintain compatibility with PostgreSQL going forward. In addition, he said that EnterpriseDB would offer support for PostgreSQL itself "in the near future".

We were curious how active EnterpriseDB had been with the PostgreSQL project so far. EnterpriseDB Co-founder and Chief Architect, Denis Lussier, is a member of three projects on the PgFoundry website. At this time, however, none of the projects are showing any real activity.

Berkus said that EnterpriseDB had contacted him and other members of the PostgreSQL community. He said that he had "every reason to believe" that EnterpriseDB would be following through on the projects on PgFoundry, and that the company intends to contribute to PostgreSQL in general. "I think it's likely they will keep some things to themselves, where their money first end up coming from." He also noted that he had talked to Astor about contributions, though nothing concrete in terms of what would be contributed, or under what licensing terms.

We also asked Berkus about corporate attention in general, and how that was affecting the project overall. He said that companies were bringing programmers and resources to PostgreSQL, and noted he was now working for Greenplum. "They're basically allowing me to work on postgresql almost full-time which is nice.".

Along with the benefits, come some side effects as well. Berkus said that it requires more effort, citing the IBM patent problem as one of the side-effects. "If we didn't have 8 or 9 contributing companies using Postgres... we could have blown that off, no way IBM would have attacked us." However, companies that use PostgreSQL in their products did not have the luxury, requiring the project to spend time rewriting code to avoid patent encumbrances.

We also asked Astor about patents, and where EnterpriseDB stood on the software patent issue. Astor said that the company is "fundamentally against [software] patents" and that he doesn't think they make sense. However, he also said that "in today's world, it makes no sense to swear that you'll never get one" and that the company may acquire "defensive" patents. "We would only have defensive plans for them, if we were to secure them for ourselves."

Since EnterpriseDB is touting the open source aspects of EnterpriseDB so heavily, it will be interesting to see how the company interacts with the PostgreSQL project over the long term. Given the terms of its license, it will probably not catch on as widely as PostgreSQL itself, but it may serve the needs of companies who are looking to get away from higher-priced packages like Oracle.

Index entries for this article
GuestArticlesBrockmeier, Joe


to post comments

Falling for proprietary hype: EnterpriseDB

Posted May 26, 2005 17:37 UTC (Thu) by ber (subscriber, #2142) [Link]

I am a bit disappointed that a proprietary company manages to get PR on LWN by doing a fork of PostgreSQL. My expectation is to shed more light on the Free Software based business.

The launch of EnterpriseDB

Posted May 27, 2005 15:26 UTC (Fri) by jeremiah (subscriber, #1221) [Link] (1 responses)

I guess I missed the point of this article. Have they added any worth while features? Revamping PGAdmin is okay, but not that important. I guess if you have a large number of embeded triggers and what not siting in Oracle, this would give you the hope migrating to a cheaper platform, but for the amount of secrecy and whatnot I don't really see this being that important. I'm more interested in additional functionality, not so much compatability. And I don't think I'm alone.

The launch of EnterpriseDB

Posted May 27, 2005 16:08 UTC (Fri) by giraffedata (guest, #1954) [Link]

I thought the point of the article was pretty clear -- to tell you that EnterpriseDB, something based on a popular open source package, exists and a little about it.

But you seem to be asking about the point of EnterpriseDB. That too is pretty explicit in Paragraph 3: Enterprise DB compatibility and a GUI Studio application. It also mentions the product being cheap.

While some may think neither of these is important, I know lots of people do. Being able to migrate an application from Oracle to something cheaper seems to be a very useful thing, and apparently that isn't as feasible with PostgreSQL.


Copyright © 2005, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds