[(Agile Database Techniques: Effective Strategies for the Agile Software Developer)] [by: Scott W. Ambler] (Englisch) Taschenbuch – 17. Oktober 2003
Kunden, die diesen Artikel gekauft haben, kauften auch
Welche anderen Artikel kaufen Kunden, nachdem sie diesen Artikel angesehen haben?
Es wird kein Kindle Gerät benötigt. Laden Sie eine der kostenlosen Kindle Apps herunter und beginnen Sie, Kindle-Bücher auf Ihrem Smartphone, Tablet und Computer zu lesen.
Geben Sie Ihre Mobiltelefonnummer ein, um die kostenfreie App zu beziehen.
Wenn Sie dieses Produkt verkaufen, möchten Sie über Seller Support Updates vorschlagen?
Agile Database Techniques One of the places data can be stored is a relational database. Relational databases store data in a table of rows and columns, and are used in traditional business applications such as banking transactions and inventory control. Full description
Die hilfreichsten Kundenrezensionen auf Amazon.com
Agile development is really only a subset of the book, with an introduction on agile development and a sales pitch for its adoption. In some sections, agile is woven into a topic, such as refactoring, that stands on its own with or without agile methodology. I can easily imagine material that started as essays on solid best practices being updated with the latest thinking, including agile.
Our organization does not use UML and has no intention to do the detailed modeling that Mr. Ambler suggests. Readers in similar situations may consider those parts looking for ideas or quickly skim them without disruption to the rest of the arguments.
I have read Scott Ambler in various contexts and his insights are always welcome. He knows the issues involved in development, including database-oriented projects, as demonstrated by his ability to touch lightly or go deep. One of the highlights here is that he articulates tradeoffs. Well, you could do this, or you could do that, and here are the issues to consider, wisely deferring the analysis and decisions to actual projects.
As far as specifics relating to databases, I thought it could have had more real-life scenarios and suggestions on how to deal with them. Some of the ideas presented were just too unrealistic for my liking.
That being said, there are a few good ideas in this book. It was a quick read too. So if you are a DBA who has no idea of agile, it might be something to start with.
Reading the book got me depressed. I sure hope agile and OO developers are more technically rigorous than the author of this book seems to be.
The first part of the book, "Foundational Skills and Knowledge", covers the challenges and how to meet them with eight excellent chapters that truly give the foundational knowledge. The next part, "Evolutionary Database Development", is comprised of seven chapters that introduce Agile techniques as they relate to DB development. Among the two strongest chapters in this part of the book are the ones covering DB refactoring and mapping objects to relational databases. This material, to me, clarified a lot of issues I had before reading this book. Part 3 is more focused on development techniques, with excellent information about concurrency control, access controls and related topics. The final part of the book is specific to general Agile implementation. You need not embrace Agile methods to learn an enormous amount from this book.
If you want to know more about this book's contents you will find a great deal of information on the author's Agile Data web site (paste the ASIN, B0000A3527, into the search box at the top of this page, select All Products and click GO). I also recommend Clifton Nock's "Data Access Patterns: Database Interactions in Object-Oriented Applications" (ISBN 0131401572), which augments this book in many respects.