Microsoft .NET - Architecting Applications for the Enterprise (Developer Reference) 2nd Edition

This book covers a wide variety of topics helpful to make architecture level decisions. Most design books discuss only design/architecture purity of certain style or the theme of that particular book. That approach is good for learning a new concept, but is far from the reality on the ground of our day jobs. Our work involves dealing with legacy systems (80's or prior, and 90's) and not so legacy systems (2000s), multiple skill levels, COTS products, multiple organizational boundaries, different skill levels of teams, multiple ongoing projects etc. Even greenfield projects need to make compromises in real world. May be not at the likes of Google and Facebook - I wonder if their payroll, vendor billing systems, other back office systems are equally sophisticated. This book talks about available options and factors to consider in multiple architecture decision scenarios and how to go about making decisions.I do not have .Net background, but thoroughly found it to be useful. This is not a book to learn architecture from grounds up and does not have much in the form of code examples. But if you have been into design and architecture already and know a bit on current and earlier trends, this is a book that puts all those in perspective and help consolidate the understanding. Nicely complements other design/architecture books and a must read for all architects.

very practical and useful book, especially it's updated to comply with the new way of building software

Very great book, with good samples. It covers in deep many of the architectural patterns found in Fowler and Evans, with a focus on C# and .NET. It also covers new patterns, such as event sourcing and CQRS. Both were eye openers to me. In particular, I liked that for event sourcing they chose a NoSQL such as RavenDB to show the examples. It just makes sense. Since I read the book I've been revisiting old projects and see that they would have done better with event sourcing. As for CQRS, I liked the authors examples on how to use it. I never heard of it before reading this book.Perhaps the only complain is that there is still a little unclear how to glue all the components together, and the companion source code seems a little bit unfinished. Regardless, this book is unvaluable, a must have in our bookshelves.

Great book. Does a nice job of presenting a practical view of DDD, and showing a potential way to apply to .Net, addressing trade offs between the way .Net might lead one to do something, and a purists view of DDD. I appreciated the explanations of the differences in approach each might lead one to to solve some problems, with a useful explanation of the tradeoffs involved.I will say that in a number of cases, a page from this book erased a mass of confusion I'd acquired from Vaughn Vernon's Implementing Domain-Driven Design. This was written in a much more concise, clear, practical manner than that book.If you're trying to actually apply DDD to build something- particularly coming from a Microsoft.Net heritage development perpsective, I highly recommend this book.

The book was a very interesting read and give guidance into what an architecture mindset should be. The emphasis on domain driven design/development is spot on as I found over the over the years that domain driven design/development is just a natural evolution of the recent agile trend. It just adds another component to any development methodology and the technique and concept explain is really sound advice. The domain driven patterns described is quite relevant and is a good read. I personally evolved my development techniques towards a domain model for application development, but it was good to discover the other 2 patterns discussed in the book (Command/Query Responsibility Segregation and Event Sourcing). Recommended reading for veteran developers who are looking to broaden their development perspective.

Great book. Informative. Good for developer who are moving to a more senior role.

I am currently a programmer in the Air Force and separating to work for a software company. I wanted a better perspective on how the civilian side of things worked. This book has great information on team dynamics and how to function with non programmer bosses. I really enjoyed the later chapters on architecture and how the book focused on the right tool for the job not necessarily the latest and greatest. I have been writing transaction script code for a long time, it works great for what I am doing and it was nice to read that it should still be considered for less complicated applications.

A book every developer, no matter what language uses, should read.The writing is enjoyable and how the book progress from a basic architecture to a more elaborate one is easy to follow.No subject is rushed. It has one chapter dedicated to talk about the architecture, followed from another one about how to implement it.The chapter talking about relational database x nosql could have been shortened.