Microsoft® Application Architecture Guide

by Microsoft Patterns & Practices Team

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.

Genres: Technology, Architecture, Computer Science, Software

496 pages, Kindle Edition

First published January 1, 2009

Reviews

[Matteo Tomasulo · Rating 2 out of 5]

It is mean to be a checklist and a reference of what you should think when define software architecture in Microsoft platform. You will find a list of common problems, and common steps and principles to follow to architect the software in the first phase of requirements analysis.

Then a list of specific architecture kind are explained with pro. and cons, when and why use it and then a list of common problem and principles to follow in the specific architecture case.

In the final part you will have microsoft technology specific architecture(asp.net, sharepoint, wpf, cloud etc...) and again listed common problem, principles, steps for the specific case.

Very intereseting the Appendix, where you will find a recap of the main Microsoft tecnology, library and resources that can be used in a particular problem.

My advise is to read the first part of the book cover to cover, and than get a speed read to the rest just to take aware of the topics and came back on when you will need it.

Only 3 star because I found the write boring and not very readable especially after the first part.

[Kapil Dhaimade · Rating 3 out of 5]

3.5*
The first part of the book is pure gold. Generic design and architecture advice which i always wish i could've got earlier.
The second half is repetitive and boring. It goes into design considerations for each type of application, from rich client to mobile app to SharePoint LOB apps. But it's so repetitive you wish they would have just made a comparison table or chart and been done with it.

Still, I highly recommend reading at least the first part of the book, the general guidelines are timeless.

[Max Savchenko · Rating 3 out of 5]

Книга представляет собой справочник с краткими описаниями предлагаемых Майкрософт технологий для каждого из основных типов разрабатываемых приложений, паттернами проектирования, на которые можно обратить внимание в том или ином случае, а также ссылками типа "Где почитать конкретно про эту вещь подробнее". Кроме того, приводится список особенностей архитектуры, на которые надо обращать внимание при проектировании того или иного ПО. Никакого конкретного кода вы тут не найдете - это книга для архитектора, в первую очередь. Издание относительно старое, стек технологий Майкрософт значительно обновился с тех пор, но помочь направить мысли архитектора ПО в нужное русло книга определенно сможет.

[Andrey Markeev · Rating 4 out of 5]

Pretty useful as a quick reference. Surprisingly, I liked the first chapter even better than the last one, despite of I couldn't ever anticipate this from the outlines.

Lack of illustrative materal and long lists of options in the second chapter make the book a bit boring.

[سامح السيد · Rating 3 out of 5]

Good, although need to be updated
I skimmed few chapters, but I can say the important parts are: part I + appendices, then part II, then part III
If you don't like to read the whole book, make sure you have a look at appendices, they are great and summarize the whole book.

[Michael · Rating 4 out of 5]

Nice reference when planning and developing frameworks or platforms.