Make the right architectural decisions up front—and improve the quality and reliability of your results. Led by two enterprise programming experts, you’ll learn how to apply the patterns and techniques that help control project complexity—and make systems easier to build, support, and upgrade—right from the start.
Get pragmatic architectural guidance on how to: Build testability, maintainability, and security into your system early in the design Expose business logic through a service-oriented interface Choose the best pattern for organizing business logic and behavior Review and apply the patterns for separating the UI and presentation logic Delve deep into the patterns and practices for the data access layer Tackle the impedance mismatch between objects and data Minimize development effort and avoid over-engineering—and deliver more robust results Get code samples on the Web.
Dino Esposito is one of the world’s authorities on web technology and software architecture. Over years, Dino developed hands-on experience and skills in architecting and building distributed systems for banking and insurance companies and, in general, in industry contexts where the demand for security, optimization, performance, scalability, interoperability is dramatically high. Dino is also a prolific author, Every month, at least five different magazines and Web sites throughout the world publish Dino's articles covering topics ranging from Web development to AJAX architectures and from data access to Silverlight and design patterns. Dino published an array of books, most of which are considered state-of-the-art in their respective areas. His recent books are Programming ASP.NET 3.5—Core Reference, Introducing Microsoft ASP.NET AJAX, and Programming Microsoft ASP.NET 2.0 Applications—Advanced Topics. Dino speaks regularly at industry conferences all over the world, including Microsoft TechEd, DevConnections, and premiere European conferences such as DevWeek and Basta.
The concepts of this books are great. I liked how Dino structured the book, starting with software architecture, covering DDD, CQRS and Event Sourcing. However, it was missing some examples on how to implement the full story. There are some code snippets for the domain model and CQRS, but it should have more for the saga implementation has just some code snippets
I found this book to be a great primer on enterprise application development. I unfortunately skipped the software engineering course during college, so I'm playing catch-up. This book is a great read to give you a broad overview of the way enterprise software is typically designed and implemented. It touches on the common layers of an enterprise application, and discusses many design patterns that successfully address the challenges of each.
I will probably read some follow up books that go into a higher level of detail on various topics, but this book was a really great place to start.
Interesting and easy-reading book on software architecture using Microsoft technologies. It also provides some helpful best practices in general regardless of the technology. It covers a wide range of many architecture aspects; from presentation patterns to business and data access layers. However, I felt that the book doesn't have a main steam. It gives you tips on every thing but there is nothing that it talks a lot about. All in all, the book is very beneficial and is a must to read for any senior microsoft software developer.
Well, I guess this is the book to beat now in .NET architectural book scene. It makes a fantastic effort in presenting the past and the present of software architecture. In my eyes every noteworthy architectural/design concept is at least mentioned if not introduced: UX First, SOLID, MVC, MVVM, 3-tier, Multi-Tier, Repository pattern, DDD, CQRS and Event Sourcing etc. There are plenty of code snippets. The authors balance theory and lessons from the trenches quite nicely. Every chapter ends with a section called "finishing with a smile", a nice bonus. :)
Skip this book and buy "Patterns of Enterprise Application Architecture" instead. It felt that every paragraph and note section in this book referenced a page number from Martin Fowlers book.