The ServerSide Interoperability Blog » Neward, object data bases and ORM issues
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.
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.
Comments