Great Book, maybe a little too "wordy"
I love this book. It really excel in giving a broader view than the mere Microsoft "stack"; for example, it does not insist on LINQ to SQL or the Entity Framework, but praises the benefits of other OR/M tools. Also, it associates design patterns with architectural decisions in a less rigid way than your classical pattern book.
I totally digged the Data Access Layer chapter.
The only thing that I struggled a little was the language: many times I felt like the concepts could have been expressed with significantly less words and maybe more examples. In fact, I often got bored and had to take a break and come back the day after.
Other than that, it's one of the best texts I've read in a while.
Excellent book
This book is well written and structured in a very intuitive way. It starts with a general and informative discussion of software architecture and then proceeds to take a detailed look at the various design decisions, patterns and components that can be found in a layered design. It references and elaborates upon many of the patterns in Martin Fowler's Patterns of Enterprise Application Architecture so a familiarity with that work is recommended but not necessarily required. It can both act as a supplement to the PoEAA in addition to standing very well on its own.
This book is required reading and highly recommended.
Great Book
This is a great book. Microsft has never been very good at guiding developers and software architects for building complex systems. I think this books fills that gap. Dino Esposito is one of the best .NET writers and he shows that in this book.
The book is very well structured and easy to read. The first part is about principles and best practices of software architecture, design and developement (UML, the role of an enterprise architect, OOP).
The second part covers each layer of an enterprise application: Business Layer, Service Layer, Data Access Layer and UI Layer. It covers the most important patterns presented in Martin Fowler's book Patterns of Enterprise Application Architecture. Some of them are:
-BL:
Transaction Script
Table Module
Domain Model
Active Record (Although Fowler categorizes this pattern as a DAL)
-Service Layer:
Service Layer
DTO
-DAL:
Plugin
Inversion of Control
Lazy Loading,
Identity Map
Data Mapper
Unit Of Work
-UI:
MVC
MVP
PM
Front Controller
There's also a sample application that shows all the patterns and practices covered in the book.
Mustknown material for the .NET architect, nicely gathered within this book
Full of known material for the experienced .NET architect, but even then useful for confirmation and reference.
Great book
Part 1 (1st 3 chapters) is kinda boring to read if you have been doing software design for years.
Fortunately, Part 2 is extremely excellent, useful and practical to the .NET development environment.
I will recommend this book to all .NET developers.
(22 reviews)
