It is not possible An interesting book that covers just what the title says: how some of today's Open Source Applications were designed. It is not possible for me to understand or be interested in every project in this book, but by concentrating on those that interested me, and generally skimming through the others, you'll get a idea of what is involved in the design of software that most of us would use, whether directly or indirectly. Some projects are covered in very general terms Hadoop Distributed File System , other expose some of the internal structures of the software Telepathy , while others give a fascinating look into how the software has developed and changed over the years Sendmail.
Probably the best way to get the most out of this book is to read those parts that interest you, but also skim through the other projects to see what ideas were rejected or implemented. You never know; the way one unknown to you project was done in the book may well guide you on how to do your own software projects better. This book can also be found online.
Oct 11, Thomas Zeeman rated it really liked it. As with any book bundling a lot of stories from different authors, the style and quality differs. A lot in some cases, although the quality tends to stay on the higher end. The various projects cover a wide range of topics i. All of them still relevant. It was interesting to read about the way various projects were designed and how things sometimes gre As with any book bundling a lot of stories from different authors, the style and quality differs. It was interesting to read about the way various projects were designed and how things sometimes grew over time.
Two things I missed there were some more graphic ways of describing the architecture of an application and some reflection on the design choices.
The later chapters sometimes did contain a few diagrams, but most chapters don't have any pictures at all. Design choices were often explained, but if there was a section on reflection or lessons learned it was relatively brief; typically a page out of a page essay. And from the ones I've read only one struck me as interesting. A revision of architecture of several open source applications. Written by apps' authors or mainteners, this book allows you to understand main architectural ideas of applications.
Get A Copy
Variety of applications communications, compilers, graph generators, Sometimes a chapter writer is not focused, and doesn't explain his application architecture properly, but that also a way of learning in this case, how not to describe an architecture. Expecting following volume A revision of architecture of several open source applications.
Expecting following volume of this serie Jun 03, Abdul Qavi rated it really liked it Shelves: 8-technical-big-data. Very informative book, a must-read for every IT professional. The book can't be rated as a whole since it consists of over 2 dozen chapters, and each chapter is written by different individual.
See a Problem?
Those chapters that are written by developers themselves like sendmail by Eric Allman, and others like Eclipse and Jitsi are excellent chapters with complete background and architecture nicely explained, while others are fairly good. Jun 28, Joey rated it liked it. Very uneaven, as is typical with this sort of book. Good chapters included llvm, bdb, bash. Too many block diagrams, and if the premise is we're not exposed to enough software architecture, why do I feel I've seen far too many of those?
Although bdb used them to good effect showing evolution over time. Looking forward to the upcoming chapters on git and ghc. Jan 03, Manzur rated it really liked it. Quite interesting and useful book about architecture of widely used software. As it's a collection of chapters from different authors, writing quality of each of them are different.
Nevertheless, I liked the book, especially "Lessons learned" part of the chapters. Jan 02, Matt rated it liked it. Like other compilations books about software that I've read, this book really works or fails depending on the author of each chapter. I enjoyed most of the chapters, loved a few of them, and groaned at a few others.
I'm looking forward to reading the second volume soon. Jul 24, Uwe Dauernheim rated it liked it. The selection of projects is not great though I can understand why. Volume II is magnitude better collection. Nov 04, Ben Sowell marked it as abandoned Shelves: ipad , technical. This book is interesting and well done, I just probably won't make it all the way through. I'll probably pick out a chapter here and there instead.
The Architecture of Open Source Applications, Volume II
Julio rated it liked it Feb 02, Patrick rated it liked it Dec 27, Blackpawn rated it really liked it Feb 28, Victor rated it really liked it Feb 22, Kevin Rejko rated it really liked it Jul 24, Duoyi Wu rated it it was amazing Mar 16, Anand Mahajan rated it it was amazing Nov 26, Jessie rated it liked it Sep 12, Lissette Hack rated it really liked it Aug 17, Matt rated it really liked it Feb 01, Samuel rated it liked it Apr 01, Bryan Cochrane rated it it was ok Jan 14, Mihai Stoicescu rated it liked it Dec 20, There are no discussion topics on this book yet. Readers also enjoyed.
Goodreads is hiring!
If you like books and love to build cool products, we may be looking for you. About Amy Brown.
The Architecture of Open Source Applications - Kitware Blog
Sign In. Access provided by: anon Sign Out. The main contributions are a synthesis of the process of authoring essay-style documents ESDs on software architecture, a series of observations on important factors that influence the content and presentation of architectural knowledge in this documentation form, and a set of recommendations for readers and writers of ESDs on software architecture. We analyzed the influence of three factors in particular: the evolution of a system, the community involvement in the project, and the personal characteristics of the author. This study provides the first systematic investigation of the creation of ESDs on software architecture.