Email	Print Reprint
	add to:
	Del.icio.us Digg Google Furl	Slashdot Y! MyWeb Blink
	TABLE OF CONTENTS Introduction Bob Walker, Gemstone Systems Derek Henninger, Progress Software Robert Greene, Versant Erik Meijer, Microsoft Christof Wittig, db4objects Patrick Linskey, BEA Craig Russell, Sun Microsystems Ten Years from Now? Data -- It's Scary Acronym Soup Business and Social Issues Back to the Social Question Different Viewpoints A Bigger Picture Question? A Service-Oriented Impedance Mismatch? Wrap Up

Christof Wittig, db4objects: I totally agree with you Erik -- no uber model. My name is Christof Wittig I'm the founding CEO of db4objects, the open source database company based in San Mateo. We started two years ago and we're certainly news in the space because we're the only object database company that ventured for the last 10 years. And there's reason to do that other than trying to get ourselves hurt.

In fact, more and more people -- and that's the power of open source and the collaborative model behind it -- more and more developers understand that relational database paradigms are not a solution for all persistence tasks in object orientated environments. And they just don't want to believe what Microsoft or Oracle often tell them: Use ORMs and they will make the pain go away. So our 15,000 registered developers and growing a thousand every month, they understand there are spaces where different persistence strategies are needed and one of the options is object databases.

Object relational mappers are a band aid for a problem, they're not the solution. Ted Neward called it very nicely the "Vietnam of computer science": Object relational mappers are subject to diminishing marginal returns. You try to solve one problems and you get two new ones.

You see it in added complexity and deteriorated performance. He says there are basically three strategies for object orientated persistence. Either embrace objects, object databases; abandon objects -- that's a good strategy -- or suffer from object relational mappers. Many developers, that for instance build applications for these cell phones, or customers of ours like Ricoh and Seagate in consumer electronics, they understand that object relational mappers simply don't work on these devices. Market research shows that basically 50% of those developers write their own persistence solution -- and that's in 2006.

So I want to say there is a case to be made for object databases and whenever you hear someone saying "Object databases have no use to object orientated developers", you just can tell them "You simply don't know the space enough".

Previous Page | 1 Introduction | 2 Bob Walker, Gemstone Systems | 3 Derek Henninger, Progress Software | 4 Robert Greene, Versant | 5 Erik Meijer, Microsoft | 6 Christof Wittig, db4objects | 7 Patrick Linskey, BEA | 8 Craig Russell, Sun Microsystems | 9 Ten Years from Now? | 10 Data -- It's Scary | 11 Acronym Soup | 12 Business and Social Issues | 13 Back to the Social Question | 14 Different Viewpoints | 15 A Bigger Picture Question? | 16 A Service-Oriented Impedance Mismatch? | 17 Wrap Up Next Page

RELATED ARTICLES Nozzle: Counteracting Memory Exploits Experts Consider Robots, Legal Issues ZigBee Alliance, DLMS User Assoc Collaborate on Metering Data Compatibility Cloud Computing: Detecting Scalability Problems Logging In C++ : Part 2		TOP 5 ARTICLES No Top Articles.