Data Access Patterns: Database Interactions in Object-Oriented Applications

Abstract

From the Publisher: 25 proven patterns for improving data access and application performance Efficient, high-quality data access code is crucial to the performance and usability of virtually any enterprise application--and there's no better way to improve an existing system than to optimize its data access code. Regardless of database engine, platform, language, orapplication, developers repeatedly encounter the same relational database access challenges. In Data Access Patterns, Clifton Nock identifies 25 proven solutions, presenting each one in the form of a clear, easy-to-use pattern. These patterns solve an exceptionally wide range of problems including creating efficient database-independent applications, hiding obscure database semantics from users, speeding database resource initialization, simplifying development and maintenance, improving support for concurrency and transactions, and eliminating data access bottlenecks. Every pattern is illustrated with fully commented Java/JDBC code examples, as well as UML diagrams representing interfaces, classes, and relationships. The patterns are organized into five categories: Decoupling Patterns: Build cleaner, more reliable systems by decoupling data access code from other application logic Resource Patterns: Manage relational database resources more efficiently Input/Output Patterns: Simplify I/O operations by translating consistently between physical relational data and domain object representations of that data Cache Patterns: Use caching strategically, to optimize the tradeoffs between data access optimization and cache overhead Concurrency Patterns: Implement concurrencyand transactions more effectively and reliably Data Access Patterns demystifies techniques that have traditionally been used only in the most robust data access solutions--making those techniques practical for every software developer, architect, and designer.

Cite this work

No public copy is stored for this record, so only the metadata is cited.

Stored only when both papers are in the corpus — 51 citations exist upstream.