Thursday, July 9, 2009

Book Review: 97 Things Every Software Architect Should Know Edited by Richard Monson-Haefel: Publisher- O'Reilly Media, Inc.: ISBN- 10: 059652269X

This book introduces new concept of book writing – Community Book. And to pleasure of Open Source supporters, book is available under Common Creative License.

Book consists of 97 aptly written essays about Software Architecture barring technical details but focused on Business and human behavior. Book does not mention any vendor and technology specific details which makes universally applicable. Unlike other Software Architecture books which are highly loaded with UML, patterns and other technical details this book covers practical day to day practices for software architecture.

97 Things Every Software Architect Should Know is crisp 200 pages long. Few of the participating authors are well known authority in software while some are hidden gems who yet to be discovered. Few of the authors have their own site and blog which will give insight into their work.

1 Allison Randal (The lead developer for Parrot)
2 Barry Hawkins
3 Bill de hÓra (Co-editor of Atom publishing protocol)
4 Brian Hart
5 Burk Hufnagel
6 Chad LaVigne
7 Clint Shank
8 Craig L Russell
9 Dan Chak
10 Dave Anderson
11 Dave Bartlett
12 Dave Muirhead
13 Dave Quick
14 David Ing
15 Doug Crawford
16 Eben Hewitt (Author of SOA Cookbook)
17 Edward Garson
18 Einar Landre
19 Eric Hawthorne
20 Erik Doernenburg
21 Evan Cofsky
22 George Malamidis
23 Greg Nyberg (author of the WebLogic companion workbook for Enterprise JavaBeans 3rd Edition and is the lead author of the book Mastering WebLogic Server )
24 Gregor Hope (Enterprise Integration Patterns: Designing, Building, and Deploying Messaging Solutions (Addison-Wesley Signature Series)
25 Jeremy Meyer
26 John Davies
27 Kamal Wickramanayake
28 Keith Braithwaite
29 Kevlin Henney (coauthor of two volumes in the Pattern-Oriented Software Architecture series: A Pattern Language for Distributed Computing and On Patterns and Pattern Languages)
30 Mark Ramm
31 Mark Richards
32 Michael Harmer
33 Michael Nygard (Release It!: Design and Deploy Production-Ready Software (Pragmatic Programmers))
34 Michael Nygard ( “Release It! Design and Deploy Production-Ready Software” - a 2008 Jolt Productivity Award Winner)
35 Mike Brown
36 Mncedisi Kasper
37 Neal Ford (Author of “The Productive Programmer”)
38 Niclas Nilsson
39 Nitin Borwankar
40 Norman Carnovale
41 Paul W. Homer
42 Peter Gillard-Moss
43 Philip Nelson
44 Randy Stafford
45 Rebecca Parsons (CTO of ThoughtWorks)
46 Richard Monson-Haefel
47 Sam Gardiner
48 Scot Mcphee
49 Stephen Jones
50 Timothy High
51 Udi Dahan
52 Vinayak Hegde
53 Yi Zhou
54 Zubin Wadia (Author of: "The Definitive Guide to Apache MyFaces & Facelets" and "Facelets Essentials: Guide to JavaServer Faces View Definition Framework")

In nutshell book spells out two vital things:

1. Role of a Software Architect
2. What should a Software Architect know apart from technical details?

In starting of book natural question come into mind that why 97, why not 96 or 98 but as you go along with book you do not care about its count. You can get details of why 97 at its site

97 Things Every Software Architect Should Know is already in bookshelf.

Disclaimer: I did not get paid to review this book, and I do not stand to gain anything if you buy the book. I have no relationship with the publisher or the author.

Further reading:
1. The Architectural Journal (Microsoft) 15

One can get more information about book and related topics from:

1. Book’s web presence
2. Amazon
3. Publisher – Oreilly
4. flipkart
5. Barnes & Noble
6. For Indian Customers
7. One More place for Indian Customers
8. Discussion at The Server Side
9. Review by Mark Needham
10. Review by Brian
11. Book Review at Dzone
12. Review at Meme Agora
13. One More Review
14. Another Review
15. The last one

1 comment:

  1. 14. David Ing's blog is