art src
Posts: 33
Nickname: articulate
Registered: Sep, 2005
|
|
Re: Next-Generation Object-Oriented Databases
|
Posted: May 26, 2008 6:45 PM
|
|
In most of the enterprise application I have been involved with, interaction with an SQL client/server DB has been a big time suck during development. It is also the most likely cause of performance issues.
At least if you get a DB with MVCC (Multi Version Concurrency Control) you don't get chronic deadlocks.
The ORM tools are complex, buggy, and incomplete. In practice the object model has always been seriously compromised by mapping to a relation database.
ORM can't work in general with a remote data store. Distribution boundaries don't disappear, databases are remote, and "don't distribute objects" is a solid principal for software architecture.
Deployment to the database has been the most problematic part of the deployment process.
There is plenty of scope for improvement on the status quo. I don't know if db4o or NGOODB's are the answer, but not solving the problem consigns us to the enormous amounts of wasted developer hours, and dramatically increased time to market for enterprises.
I am not giving up on the idea that there is something better than SQL + JPA.
|
|
Previous Topic
