NDO makes Persistence simple
Business applications always work with data. So there always has to be a means to store and retrieve data, preferably using databases that allow querying data rows according to certain criteria. On the other hand, the best way to code business applications is to use object systems. Storing an object system in a database and retrieving it again is a laborious and error-prone task. Every navigation path between different classes needs a query to fetch the state of the related objects. The effort for accomplishing data access (in lines of code, time and money) explodes exponentially with the complexity of a system, in proportion to the numbers of classes involved. The example shows this in detail.
Here NDO and it’s concept of transparent persistence enters the stage. Transparent persistence means that nearly all of the code normally written for data access just disappears. Objects are stored and reloaded automatically; they are just there when you need them. The aspect of persistence is only visible if you wish so, for example in transaction management or in queries for certain objects.
The benefit of using NDO is generally 40% to 70% less code for business applications.