Data Access Patterns: Database Interactions in Object-Oriented Applications 1st Edition
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Customers who viewed this item also viewed
Customers who bought this item also bought
From the Back Cover
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, or application, 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 concurrency and 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.
About the Author
Clifton Nock is a senior software architect at PeopleSoft in Denver, Colorado. He spent five years at IBM designing programming interfaces that simplify access to the iSeries operating system and its integrated database and holds nine U.S. patents relating to this work. He has taught several programming courses at the University of Minnesota and presented at technical conferences worldwide. He holds an M.S. in Computer Science from the University of Minnesota.
- Item Weight : 1.85 pounds
- Hardcover : 400 pages
- ISBN-10 : 0131401572
- ISBN-13 : 978-0131401570
- Dimensions : 7 x 1 x 9.25 inches
- Publisher : Addison-Wesley Professional; 1st edition (September 1, 2003)
- Language: : English
- Best Sellers Rank: #2,650,787 in Books (See Top 100 in Books)
- Customer Reviews:
Top reviews from the United States
There was a problem filtering reviews right now. Please try again later.
The most interesting patterns are in resource and cache. Decoupling and concurrency patterns (e.g., data accessor, active domain object, layers, transactions, optimistic/pessimistic lock etc.) are well known and the contents are a bit too light to be very useful, yet the concepts are giving readers some directions.
In resource patterns, some interesting patterns are presented, particularly resource timer automatically releases inactive resource, retryer enables fault-tolerance for data access operations.
In cache patterns, cache collector purges entries whose presence in the cache no longer provides any performance benefits; cache replicator replicates operations across multiple caches.
There are some areas to be improved, first, author should consolidate pattern names with other pattern authors, e.g., data accessor is also known as data access object, active domain object is similar to active record, paging iterator is close to value list handler (though value list handler is more decoupled from underlying data store), the point is, one of the important benefits and purposes for documenting patterns is to build common vocabularies among designers, using different names for same or similar patterns is defeating this purpose. The same pattern name should be used and may be presented as a variation of the original pattern.
Secondly, the examples given in the book is a bit too simple, sometimes, the examples might not justify or validate the interface abstraction is generic enough to handle real world problems, so some tweaking and modification to the pattern would be expected.
Overall, the book is well organized, and contents are easy to follow, most patterns come with class diagrams and sequence diagrams. Good for designers who want to decouple data access from rest of the application, utilize cache to minimize data access and thus boost application performance, manage resources in an efficient and leaking-proof way.
However, I wouldn't say it's a complete design (which it doesn't claim to be). I still found myself picking and choosing which patterns to use as is, which to modify to my liking, and which to discard.
Also, I was left with the impression that the book didn't give enough coverage to handling collections of objects. The material is mostly geared toward working with a single object, which is understandable. I just think it would have been helpful to have more discussion about handling collections. For example, what should happen when you request to load an object, but the criteria you passed to the loading mechanism results in data for more than one object being retrieved from the database? Hand back the first object? Raise an exception? If it's covered in the book, I missed it.
Further, I would like to see more discussion about WHEN to refresh an object from the underlying database and when to save to the database. I always struggle with that timing issue. Having studied EJB, I like how entity beans keep your bean in synch with the underlying database. But the EJB container intercepts calls and makes those things happen. When coding the persistence layer myself, that's not an option. So, again, this is something I'd like to see some light shed on.
Overall, though, a great book if you're interested in reading up on persistence layer patterns.
While prototyping the model, I encountered a lot of consideration of what is the best approach for certain implementation (mainly on JDBC). While looking into a few of designing books, I found this Data Access Patterns book that fits into my research needs. I have read other book such as Designing Flexible Object Oriented System with UML and not able to apply the concept or see solution in it. It is simply a conceptual book. No practical examples at all.
Mr. Nock has explained the design patterns very clearly in each chapter by using JDBC as a media. The examples are very easy to understand as compared to Design Patterns Explained. I am not able to understand codes that implementing graphics in that book.
Mr. Nock addressed the pros and cons of the patterns. Many techie books do not even bother to talk about pros and cons.
The author has chosen the right title for the book, I realized that many times author received a poor rating because reader expect different contents based on the title of the book.
The feature I liked the most - the ¡§Applicability¡¨ section on each chapter. Unlike other patterns book, the author explains the concept and gives example of "what" and "when" to use certain design pattern. This section is pretty much the answer for my thesis obstacles. The answer is in this book!!
Minor typos do exist such as in page 390 roll back instead of rollback.
In concurrency chapter, author may have mis-used the term of updates locking. It should be Lost Updates instead of Missing updates. Concurrency chapter looks like UDB Lock Concurrency architecture.
Additional note - would like to see the quality aspect in each of the patterns.
Overall, the book is very well structured, explained and thoughtful.
Thank you Mr. Nock !! This is a perfect book for my thesis.
Looking forward to read your future publish.
Top reviews from other countries
Of particular interest were the patterns concerned with mapping relational data to domain objects, which I found invaluable in my own work.
But it's all fanatstic.
Everything is presented clearly, concisely, and all the information you need is there and tremendously accessible.
Case in point -- I work in Java (the book's examples language), C++, and PHP, and the concepts in the book are so clear, it's easy translating them between the three.
This guy writes all code books in my perfect world!