InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Application Architecture Guide 2.0 Beta1 Published

Posted by Abel Avram on Nov 07, 2008

Sections
Development
Topics
Artifacts & Tools ,
.NET ,
.NET Framework ,
Architecture
Tags
Microsoft ,
Patterns and Practices

Microsoft's patterns & practices group has published Application Architecture Guide 2.0 Beta1, a book containing principles, patterns and practices for designing the architecture of applications built on the .NET Framework. The intended audience is solution architects and development leaders.

The book consists of the following parts:

  • Part I, "Fundamentals," provides you with the fundamentals to understand architecture design techniques and strategies.
  • Part II, "Design,” provides overarching design guidelines and best practices that can be applied to any application type or application layer, including how to design communication and plan for services.
  • Part III, "Layers,” provides architecture and design approach as well as best practices for each layer, including presentation, business, service, and data access.
  • Part IV, "Quality Attributes,” provides specific guidance on quality attributes such as security, performance, etc.
  • Part V, "Archetypes – Design and Patterns,” provides patterns and design frames for each application type archetype, including service applications, web applications, rich client applications, rich Internet applications and mobile applications.

According to patterns & practices Principal Program Manager and co-author J.D. Meyer, the book tries to help with:

  • Choosing the right architecture for your application.
  • Choosing the right technologies
  • Making more effective choices for key engineering decisions.
  • Mapping appropriate strategies and patterns.
  • Mapping relevant patterns & practices solution assets.

The guide is taking into consideration the following factors: application types, architecture styles, architecture frames, scenarios, quality attributes, and requirements/constraints as shown in the image below:

architecture

The guide uses the following reference architecture:

arch

Other notable patterns & practices guides are: Enterprise Library v4.1, Acceptance Test Engineering Guidance.

 

No comments

Watch Thread Reply

Educational Content

Jesper Boeg on Priming Kanban

In this interview, Jesper Boeg, author of the new InfoQ book – Priming Kanban, discusses the keys to using Kanban effectively, and how to get started if you are currently using other approaches.

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.