- Series: Patterns & Practices
- Paperback: 496 pages
- Publisher: Microsoft Press; Second edition (November 4, 2009)
- Language: English
- ISBN-10: 073562710X
- ISBN-13: 978-0735627109
- Product Dimensions: 7.5 x 1.5 x 9 inches
- Shipping Weight: 2.4 pounds
- Average Customer Review: 18 customer reviews
- Amazon Best Sellers Rank: #1,118,766 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Microsoft® Application Architecture Guide, 2nd Edition (Patterns & Practices) Second Edition
Use the Amazon App to scan ISBNs and compare prices.
The Amazon Book Review
Author interviews, book reviews, editors picks, and more. Read it now
Customers who bought this item also bought
Customers who viewed this item also viewed
Top customer reviews
There was a problem filtering reviews right now. Please try again later.
One of the biggest myths in software development is that it is detrimental to keep the architecture extremely simple, especially at the beginning. The argument is that you won't have enough flexibility later on as your app grows. Nothing could be further from the truth. If you've kept things simple, it is usually not a big deal to scale up the complexity of the app. But the flip side is almost never true. If the architecture is overly complex, it is usually very difficult to refactor it to a more manageable, higher-performing place. I can't tell you how many brittle OO systems I've seen that eventually collapse because OOP has inherent extensibilty and maintainability problems, especially when you're building agile apps that need to respond to change quickly. ORM makes those problems even worse.
In addition to the Guide, I'll use Erl's SOA books or Dino Esposito's references, and others, but the Guide is usually the first place a I begin to make certain I do not make any expensive mistakes along the way.
I find it important to mention that this book had more than 30 collaborators from within Microsoft, its partners and its customers, so its depth in knowledge is expansive.