||db4objects provides an object data base management system. While ODBMS technology has proved a niche technology over the years, it is poised as another means of achieving interoperability. db4objects describes their object DB as native to Java and .NET. For example, the software supports class aliases that reconcile the different naming conventions so that Java and .NET db4o instances (clients or servers) can share persisted objects without the need to deploy classes to the server. Of course, there is more.
TheServerSide Interop Blog Charter Blogger Ted Neward [shown here] recently took a look at the db2objects space as part of a broader interview on TheServerSide.com. Here we provide some highpoints from that discussion, as well as a link to Ted Neward’s new TSS.com TechTalk on Object/Relational Mapping and the Vietnam of Computer Science.
As we begin our story, Ted notes that he is wearing a DB4Object shirt.
What has happened … and … I am obviously wearing their shirt, the DB4Object guys, one of the things that they have done, a couple of things that they have done differently that I find myself agreeing with, what they have done first of all is they have not stood up and said, ‘We want to replace the relational database in the IT world.’ As a matter of fact, for a long time they were aiming squarely at the embedded space where guys are still rolling their own persistence engine. Like guys are sort of writing Java object, serialization objects to disk and then folding them back up. Read more »