Microsoft® .NET: Architecting Applications for the Enterprise (Pro-Developer) at Dominant Systems Book Store

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.

Customer Reviews & Comments
This book seemed really promising from the title and mainly its author (Dino Esposito), who is one of the best .NET writers out there. It took me a while to buy it though, because for weeks I tried in vain to find its table of contents, to know exactly what I was buying. Having failed at finding one, I decided to just take a chance and buy it anyway, and I don't regret, it is a good book. I would say the target audience is intermediate to senior developers who are getting into software architecture, or architects who work on a database-centric way and want to get an update to the current buzzwords, such as domain model pattern, repositories, services, AOP, POCO, OR/M, DDD etc. This book does not try to be a definitive source on any of those topics, but more like an introduction and a reference; the authors make a good job at pointing for resources for those who want to get more dense information. Books like Martin Fowler's "Patterns of Enterprise Application Architecture", the GoF classic Design Patterns book and Eric Evan's "Domain-Driven Design" are mentioned dozens of times, so people who have already read those books may not have lots of new stuff to see here, unless they are looking for a lighter reference or want to see how some of those ideas can be applied on .NET. So, for those like me who have spent a few days on Google trying to find out the book's ToC, here is a summarized version, with some of the topics covered in parenthesis: Part 1 - Principles 1 - Architects and Architecture Today (software life cycle, agile methodologies etc) 2 - UML essentials (UML models and usage, use-case diagrams, class diagrams, sequence diagrams) 3 - Design Principles and Practices (OOD, AOP) Part 2 - Design of the System 4 - The business layer (transaction script pattern, table module pattern, active record pattern, domain model pattern, DDD) 5 - The service layer (service layer pattern, remote façade pattern, adapter pattern, SOA, AJAX service layer for rich web frontends) 6 - The data access layer (plugin pattern, Inversion of Control, data context, query services, concurrency, lazy loading, OR/M, stored procedures, dynamic SQL) 7 - The presentation layer (MVC, MVP, presentation model pattern, choosing a UI pattern, MVP in web presentations, MVP in Windows presentations) 8 - Final thoughts

Back To Top