Welcome to Issue 12 of the Journal. The theme this time is "Web Architecture." I'm sure I don't need to tell you how important the Web has become in recent years for architects in almost all organizations. After speaking with many about designing for the Web, however, one common motif is the need to adapt — to take architectural principles that have worked in the past and refactor them for the Web. As a result, I've tried to keep this in mind when selecting the articles for this issue.
Leading the issue with the topic of Web 2.0 in the Enterprise, we have returning author Michael Platt. Michael discusses some of the technology, data, and people principles of Web 2.0, and then maps them to how they can be used inside and outside the enterprise. Following Michael's article, Gianpaolo Carraro, Fred Chong, and Eugenio Pace introduce the concept of a Service Delivery Platform. Building on their work in the Software as a Service space, they cover what's needed to enable efficient software delivery on the Web today. Danny Thorpe from the Windows Live team follows with an article that explores some of the complexities of cross-domain communication in the browser. Using a novel analogy, Danny looks at a set of techniques that can be used to overcome this challenge. We also have Michael Pizzo's excellent article on an application-oriented model for relational data. With data being a huge part of many applications on the Web, Michael takes us through some of the challenges with database and application schemas today, and introduces a framework to better integrate the two.
In my introduction to the last issue, I mentioned a former colleague of mine, Pat Helland. For this issue, I caught up with Pat, who has recently returned to Microsoft as an Architect in the Visual Studio team. I ask Pat about the role that he is going to be playing, and some of his colorful thoughts on how to become an architect. Following Pat's interview, we have an article from Peter Hammond. Peter takes us on a journey over the past 10 years, looking at some data issues that many people will be able to relate to, and introducing a technique for reliable exchange of data over the Web today. To wrap up this issue, we are lucky to have an article from Jesse Kaplan. Jesse takes us through some of the architectural considerations in the next release of the .NET Framework, and introduces a model for creating reliable and resilient add-ins.
Well, that wraps up another issue. Talking of adapting, here at The Architecture Journal, we are always trying new things—a lot, based on what we hear from you. If you have feedback or ideas for upcoming themes and articles, we'd love to hear them, in order to make this a better publication for you. You can reach us at firstname.lastname@example.org.
By Michael Platt
Discover the technology, data, and people elements of a Web 2.0 architecture and how they can be used inside and outside the enterprise.
By Gianpaolo Carraro, Fred Chong, and Eugenio Pace
Explore the use of a Service Delivery Platform to enable efficient software delivery for the Web.
By Danny Thorpe
Today's browsers work inefficiently across multiple domains. Learn a new technique for developing Web sites that can share information.
By Michael Pizzo
Often, the shape of data in a database does not match the application that interacts with it. See how a conceptual model can be used to overcome this.
Pat Helland is an Architect in Microsoft's Visual Studio team. Get the update on his career and thoughts on becoming an Architect.
By Peter Hammond
Many patterns exist for the exchange of data over the Web. Learn recommendations and pitfalls to avoid from a series of experiences.
By Jesse Kaplan
Learn about some of the advanced architectural concepts in the next release of the .NET Framework that support a resilient and reliable add-in model.
This article was published in the Architecture Journal, a print and online publication produced by Microsoft. For more articles from this publication, please visit the Architecture Journal Web site.