The .NET framework has become the platform of choice for many enterprise
applications. Not surprisingly, many .NET concepts parallel those in CORBA
and J2EE. The benefit of hindsight gives .NET architects and developers the
opportunity to imitate the success while avoiding the pitfalls inherent in
complex distributed development. This is especially true for data
persistence, which often gets less attention than it deserves.
Issues with data persistence are often not discovered until the later stages
of development and testing, when the options for addressing them are limited
and expensive. A well-designed data persistence layer can drastically improve
the performance of the entire application, if it's addressed throughout the
development process.
This article outlines best practices for developing advanced data persistence
in a .NET application. It discusses the dev... (more)