“We cannot afford to keep breaking up objects into SQL databases and then to reconstitute them when we load them into the program.”

“It reduces the amount of code needed to do same thing than standard Data Access Layer technologies. It also reduced time to develop new functionality. Faster time to market, less code, less errors.”

“The database engine is fast for data read and writes. From what we’ve done, it’s about 5 to 10 times faster than SQL Server 2005.”

“The first tests with Versant have shown that it is roughly 10 times faster than MySQL when measured on complex objects.”

“We picked Versant ODBMS as its technology proved excellent in terms of usability, robustness, and performance. We will also benefit by reduced development cost and quicker time to market.”

“Often the best way to make powerful applications is by using object-oriented programming to its fullest. When you use a rich domain model, using an object database has big payoffs. Architects too often assume that storing the state of their objects in a relational database is the right nswer. Often, it’s not, leading to awkward object to relational mappings that provide reduced performance. In short, use the right tool for the job.”