Persistence of the state of a system that can be taken for granted, without the need of explicit read, write or translate complexity in the source-code.
It has the same effect as a VM that would never crash: you could simply write plain Java classes and keep all your objects in RAM.
-No more SQL code.
-No more JDBC driver.
-No more database and app server licensing.
-No more database and app server installation and configuration every time someone wants to deploy, develop or demonstrate your system.
-No more database and app server administration.
-No more database and app server glitches.
-No more EJB overhead.
-No more code pre or post-processing convolution.
-No more proprietary VMs.
-No more data-model to update.
-No more encapsulation breaking and dependency inversions.
-No more restrictions on the data-structures, algorithms and query languages you can use.
-No more performance penalties.
Transparent persistence is also known as orthogonal persistence.
"The principal gains provided by orthogonal persistence are:
-Improved programming productivity from simpler semantics.
-Without persistence, ad hoc arrangements for long term data storage, and data translations are necessary.
-Type checking protection mechanisms operate over the whole environment.
-Referential integrity is automatically supported."
--Graham Kirby
Back to:
StartingPoints.