Microsoft® Application Architecture Guide
and over one million other books are available for Amazon Kindle .
Learn more
| |||||||||||||||
 Trade In this Item for up to £10.85
Get an extra £5 when you trade in books worth £10 or more until June 30, 2012. Trade in Microsoft Application Architecture Guide 2nd Edition (Patterns & Practices) for an Amazon.co.uk gift card of up to £10.85, which you can then spend on millions of items across the site. Trade-in values may vary (terms apply). Find more products eligible for trade-in.
|
Frequently Bought Together
Product details
|
Product Description
Product Description
Get the definitive guide on designing applications on the Microsoft application platform—straight from the Microsoft patterns & practices team. Learn how to choose the most appropriate architecture and the best implementation technologies that the Microsoft application platform offers applications developers. Get critical design recommendations and guidelines organized by application type—from Web, mobile, and rich Internet applications to Office Business Applications. You’ll also get links to additional technical resources that can help with your application development.
Inside This Book
(Learn More)
Suggested Tags from Similar Products(What's this?)Be the first one to add a relevant tag (keyword that's strongly related to this product)
|
What Other Items Do Customers Buy After Viewing This Item?
Customer Reviews
Most Helpful Customer Reviews
Format:Paperback
This is a very usefull book if you are thinking of rewriting an old application portifolio and need to look into system architecture. Usually I am not very impressed by the Microsoft books written by a herd of their emplyees. This, however, gives a clear presentation of the layers in modern software development. I have bought 4 copies as one after the other of my copies have been "borrowed" by my collegues at work. This is the second edition, and it was written in 2009, and I hope we will see a 3.edition soon.
Most Helpful Customer Reviews on Amazon.com (beta)
Amazon.com:
8 reviews
18 of 22 people found the following review helpful
A must have for the .NET Architect, Developer, and PM
16 Nov 2009
Format:Paperback|Amazon Verified Purchase
Man, was I glad to see them print this thing. I had bugged them about it, but they said it wouldn't pay for itself. It's good to see they changed their mind. I have been lugging it around in a binder, and that had been less than pleasurable.
I like keeping this with me because it serves as great reference of all the things I am supposed to remember, but often forget. When it comes time to begin a new architecture I like having my valuable books nearby, and this is one of them.
This book is packed with guidance on Mobile applications, Rich client applications, Rich Internet applications, Service applications, and Web applications built with .NET. The solution guidance provided in this book is all 100% .NET and Microsoft centric. It maps all the important aspects of software architecture to ways to implement them in .NET or with Microsoft products. This is the compass you need to find out what Microsoft has to offer for building different types of architectures.
The book includes individual chapters on designing Mobile applications, Rich client applications, Rich Internet applications, Service applications, Web applications, Hosted and Cloud Services, Office Business applications, and SharePoint LOB applications.
The book also includes some nice appendixes. They include the Microsoft Application Platform, Presentation Technology Matrix, Data Access Technology Matrix, Integration Technology Matrix, Workflow Technology Matrix, patterns & practices Enterprise Library, and a patterns & practices Pattern Catalog.
The book primarily focuses on architecture, but each chapter provides resources for guidance on the details of implementation for the technologies mentioned in that chapter.
The book focuses on the technical aspects of .NET architecture. It does not cover the soft skills needed to be an architect, or cover the customer facing skills need to communicate with the business stakeholders. You won't find much on process either, just an overview. These missing topics have not taken away from the book, they have made it a stronger book. There are plenty of resources on how to execute the soft skills and architecture process. This book concentrates on how to communicate with the development team through solid design and well known patterns and principles.
If you are a .NET Architect, Developer, or Project Manger of a .NET team, you should have this book at your side. As a matter of fact, I would recommend making one of your interview questions for your team members - "Tell me what your favorite part of the Microsoft Application Architecture Guide 2nd Edition is?" If the candidate does not have a favorite part, you get back that hour you almost wasted on them.
I like keeping this with me because it serves as great reference of all the things I am supposed to remember, but often forget. When it comes time to begin a new architecture I like having my valuable books nearby, and this is one of them.
This book is packed with guidance on Mobile applications, Rich client applications, Rich Internet applications, Service applications, and Web applications built with .NET. The solution guidance provided in this book is all 100% .NET and Microsoft centric. It maps all the important aspects of software architecture to ways to implement them in .NET or with Microsoft products. This is the compass you need to find out what Microsoft has to offer for building different types of architectures.
The book includes individual chapters on designing Mobile applications, Rich client applications, Rich Internet applications, Service applications, Web applications, Hosted and Cloud Services, Office Business applications, and SharePoint LOB applications.
The book also includes some nice appendixes. They include the Microsoft Application Platform, Presentation Technology Matrix, Data Access Technology Matrix, Integration Technology Matrix, Workflow Technology Matrix, patterns & practices Enterprise Library, and a patterns & practices Pattern Catalog.
The book primarily focuses on architecture, but each chapter provides resources for guidance on the details of implementation for the technologies mentioned in that chapter.
The book focuses on the technical aspects of .NET architecture. It does not cover the soft skills needed to be an architect, or cover the customer facing skills need to communicate with the business stakeholders. You won't find much on process either, just an overview. These missing topics have not taken away from the book, they have made it a stronger book. There are plenty of resources on how to execute the soft skills and architecture process. This book concentrates on how to communicate with the development team through solid design and well known patterns and principles.
If you are a .NET Architect, Developer, or Project Manger of a .NET team, you should have this book at your side. As a matter of fact, I would recommend making one of your interview questions for your team members - "Tell me what your favorite part of the Microsoft Application Architecture Guide 2nd Edition is?" If the candidate does not have a favorite part, you get back that hour you almost wasted on them.
9 of 10 people found the following review helpful
Great Reference
12 Dec 2009
Format:Paperback|Amazon Verified Purchase
I didn't use the first edition of the guide as much as I thought I would when it first came out oh so many years ago. But when the new 2nd edition was released I was interested to see what changes they had made. I was very surprised to find it so useful. There is a lot of great descriptions for the different architectures possible with the .NET framework. I found this to be a great refrence for documenting architectures for the projects I work on. It helped me organize my thoughts, and consider items to include (and to leave out) of my architecture documentation. One thing I noticed was the printed version is different than the PDF available for download from the CodePlex web site. Not sure why they are different, but I found the print version a bit better to follow.
5 of 6 people found the following review helpful
Covers a lot, but a bit too general
14 Sep 2011
Format:Paperback|Amazon Verified Purchase
I think this book is valuable in the sense that it addresses most of the issues you'll face when building an application. My only criticism is that the advice is very general and high-level. For experienced devs, you've probably heard it all before. For less experienced devs, I think this is a good starting point. In the end though, I wish the authors would have spent a little more time on more "philosophical" issues. The reason I say that is because no matter how much knowledge and technical skill you have at your disposal, if you don't have a mindset of keeping things simple, or being very focused on performance and scalability, you can get lost in a hurry. For example, the decision to use ORM may sound great in concept, but it violates just about every rule I believe that a developer should keep foremost in mind (i.e. ORM is not simple and it doesn't perform or scale very well, particularly compared to higher performance alternatives).
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.
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.
Were these reviews helpful?
Let us know
Listmania!
Look for similar items by category
Look for similar items by subject
Feedback
- Would you like to update product info or give feedback on images?
- I am the Author, and I want to comment on my book.
- I am the Publisher, and I want to comment on this book.
|
