The Microsoft patterns & practices team are up to it again.  Fresh on the heels of releasing the Developing Applications for SharePoint 2010 guidance, they've recently released part 1 of the Windows Azure Architecture Guidance.

What's in the Windows Azure Architecture Guide - Part 1?

Click here to download the guidance

Quick Links

• MSDN Site: SharePoint Guidance
• Future Friendly URL: http://www.microsoft.com/spg
• Download: SharePoint Guidance - November 2008
• CodePle Site: http://www.codeplex.com/spg
• Community Forum: http://www.codeplex.com/spg/thread/list.aspx

Guidance at a Glance

This guidance helps architects and developers build SharePoint intranet applications.  The guidance contains a reference implementation that demonstrates solutions to common architectural, development, and lifecycle management challenges.  This guidance discusses the following:

• Architectural decisions about patterns, feature factoring, and packaging
• Design tradeoffs for comon decisions many developers encounter
• Implementation examples demonstrated in the reference implementation and in the QuickStarts
• How to design for testability, create unit tests, and run continuous integration
• Set up of development, build, test, staging, and production environments
• Managing the application life cycle including upgrade
• Team-based intranet application development

The following areas are not discussed in this version of the guidance:

• Content-oriented sites that use web content management
• Internet and enterprise-scale SharePoint applications
• Multilingual SharePoint applications
• Scale or security testing of SharePoint applications

A lot of exciting things came out of day #1 at the PDC.  I’m sure you’ve already started to see/hear about the great technology that we are unveiling.  During the keynote, I saw laptops being pulled out and I’m quite sure there are tons of blogging going on in the blogosphere

Today, Ray Ozzie kicked off the 2008 PDC with a keynote that basically laid the foundation of our software plus services strategy and highlighted the key investments we've been making over the last few years in bringing our cloud platform to fruition.  In his talk, he focused on the landscape as we see it in 3 tiers:

• Experience Tier – The experience tier focuses on the end-user and their user experiences with the desktop/mobile device
• Enterprise Tier – The enterprise tier focuses on people interaction with enterprise systems and system-to-system interaction within the enterprise
• Web Tier – The web tier focuses on leveraging the web as the backbone for next generation computing.  Our cloud computing initiative is focused on leveraging the web through providing scalable hosting services for applications services.

Windows Strata becomes Windows Azure

During the keynote, Ray made the "formal" announcement of the name of our new cloud platform.  For those of you who knew this as codename "Windows Strata", the platform has now been officially branded as Windows Azure.

Windows Azure provides a hypervisor-based model for providing secure and scalable hosting services.  It separates the application/service being hosted from the underlying operating system.  It is also important to note that Azure is not only for managing server infrastructure, but also web services as well and provides an end-to-end approach for accomplishing this.  At the heart of Azure is a "Fabric controller" which dynamically manages resources within the data center to preserve the health of services/applications that are deployed to the Azure Platform.

Windows Azure will provide support for both managed (.NET) and unmanaged code which essentially allows you to host non-.NET applications within this cloud fabric.  From a developer perspective, developers will be able to take advantage of this platform locally, through the Azure SDK and supporting tools for Visual Studio, that'll provide facilities to support the development/debugging of cloud-based applications.  Through a "publish" operation in Visual Studio, developers will be able to publish their solution to the Azure services Developer Portal.

The Azure Services Platform consists of the following platform technologies:

• Windows Live Services
• Microsoft .NET Services
• Microsoft SQL Services
• Microsoft SharePoint Services (this is not to be confused with WSS)
• Microsoft Dynamics CRM Services

The Azure platform should also not be confused as a replacement of our one-premise offerings, but rather a complementary, cloud-based equivalent.  our on-premise offerings as a part of our strategy include:

• SQL Server 2008
• BizTalk Server
• SharePoint Server
• Dynamics CRM
• Windows Server
• Systems Center

The platform will provide capabilities that allow developers to model the services deployed on the platform.  Service modeling consists of:

• Roles and Groups (e.g. who has access to the services that are being published and what operations/actions they can perform
• Channels and Endpoints (e.g. defining how the services will be exposed and over what transport protocols)
• Interfaces
• Configuration Settings

During the keynote, there were partner demonstrations of solutions that are already taking advantage of the Azure Services Platform.  Jonathan Greensted, CEO of Sentient, gave a demonstration of a solution that his company has been working on called, Bluehoo.com (http://m.bluehoo.com) that integrates cloud-based services with mobile devices.  You can download and starting playing with the solution from http://m.bluehoo.com.  In addition, Shawn Davison, VP of RedPrairie, a Supply-chain manufacturing solutions firm, demoed a "one button" product recall orchestration running on Windows Azure and leveraging .NET services like workflow.

Bob Muglia came on stage and discussed our roadmap leading into 2009+.  He focused on the theme of the "5th generation computing".  In his discussion, he highlighted where we've been and where we're going

• 1970s - Monolithic
• 1980s - Client-server
• 1990s - Web
• Today - SOA
• 2009+ - Services

Bob’s “evolutionary” discussion provided additional context to what Ray covered in his keynote and further solidified our messaging around the Windows Azure platform and the investments that we’ll be making from now, until we ship.

What's in Microsoft .NET Services?
.NET Services (formerly known as BizTalk Services) are a set of Microsoft hosted, scalable, developer-oriented services that provide key building blocks upon which developers can create cloud-based or cloud-aware applications.  Essentially, it breaks down into the following 3 components:

• A full end-to-end service bus solution – Makes it easy to connect disparate applications over the internet
• Facilities that support Identity/Access Control – Provides an easy way to control web applications and services using standards-based identity providers, including enterprise directory services such as Active Directory and web-based identity stores such as Windows Live ID
• Workflow Services – Provides a highly scalable host for running workflows in the cloud. 

What's in SQL Services?
SQL Data services extend the capabilities of SQL Server to the cloud as web-based services, which enable you to store your data in a highly-scalable and internet-facing distributed database service infrastructure.  It contains the following key components:

• Database
• Data Sync
• Reporting
• Data Mining
• ETL
• Reference Data

What about Microsoft Online?
Our Microsoft Online Strategy still remains intact and will take advantage of the new Windows Azure platform as it evolves.  The Microsoft Online platform is geared at addressing many customer challenges we've heard, including:

• Best in class collaboration
• Staying up-to-date with software versions/patches/updates
• Lower, predictable costs
• Scarce IT resources
• High Security
• High Availability

NOTE: It is important to note that the current version of Microsoft Online IS NOT built on the Windows Azure platform.  Over time, it will take advantage of our investments in Windows Azure.

Can customers host Windows Azure within their own data centers?
This question was asked several times within today’s breakout sessions.  The answer to this is that as the features/capabilities of Windows Azure evolve, we (Microsoft) will take a look at the capability stack and identify key features of Windows Azure and roll it into our enterprise server products.  There is still significant value within our enterprise server platform and overtime, those products will benefit from the rich investments being made in Windows Azure.

When are we going to ship Windows Azure?
Answer: When it’s ready. :-)  

Essentially, we’re targeting some time in calendar year 2009, however, we’re largely basing our release on when our customers think that it’s ready to be released, and not a moment sooner.  We will follow a similar process that we’ve followed with CTP services we’ve already released and will be doing frequent updates.  However, the final ship date was not disclosed.

Are there any resources available to learn more about Windows Azure?
You can find more information about the Azure Services Platform, including whitepapers, SDK and tool downloads, datasheets, and a link to sign-up for a test/dev account to the Windows Azure cloud platform at the Azure Services Platform website.

That about sums up day #1.  I hope you find this recap helpful.

Microsoft Application Virtualization (App-V) version 4.5

Infrastructure Planning and Design guides have been updated with the introduction of Microsoft Application Virtualization (App-V) version 4.5.  Download the ensire IPD series or download the entire IPD series or download the individual guide.

This guide provides you with key information to bring your infrastructure up to date, saving you time and money.  Find out how App-V's HTTP streaming of virtual applications from an IIS server will impact your performance and scalability decisions.  Using App-V 4.5 with its many new features to strategically plan your application virtualization infrastructure can hep you avoid problems before they begin, allowing you to serve your customers more accurately and reliably.

Use these guides to determine the scope of the services to be provided and choose to partially or completely redesign your infrastructure. Have confidence in knowing that the steps in each phase are described in detail and that the necessary tools are provided to manage the process.

Join the Beta

Additional Infrastructure Planning and Design series guides are available as beta releases on the Connect Web site. They are open beta downloads. See below for instructions on how to access the beta guides.

To join the Infrastructure Planning and Design Beta, follow these steps:

1. Visit the Infrastructure Planning and Design Beta on the Microsoft Connect website.
2. Sign in using a valid Windows Live ID to continue to the invitations page.
3. Scoll down to Infrastructure Planning and Design.

If you have not previously registered with Microsoft Connect, you might be required to register before continuing with the invitation process.

The Best Practices Resource Center for SharePoint Server 2007 has been recently launched on our TechNet site.  The intent of the site is to provide a resource for guidance and best practices in efforts to avoid common pitfalls and keep your Office SharePoint Server 2007 environment available and performing well.  The best practices cited within the resource center is based on real-world experience from Microsoft Consulting Services and the SharePoint Product Team.

Came across this blog post by Dare Obasanjo, PM on the Windows Live Team, about our approach to data center management where he highlights a paper written by Michael Isard of Microsoft Research, called Autopilot: Automatic Data Center Management, which describes the technology that Windows Live and Live Search uses to manage their web server farms. 

The paper provides a high-level overview of AutoPilot, while Dare’s post goes into more of its practical implementation.  Both are definitely worth reading :-)

Announced on the SharePoint Team Blog, the SharePoint Deployment Planning Services program has been launched and is geared at helping our Software Assurance (SA) customers sucessfully plan and deploy SharePoint Products & Technologies.  I think this program provides a great resource for those customers who are struggling to make sense of SharePoint technologies or are trying to uncover proven "best practices" around how to properly deploy and implement SharePoint-based solutions.

During my time as a Technology Architect within the Reston, VA Microsoft Technology Center, I worked with a number of customers in definining SharePoint-based solution architectures where we covered topics such as understanding SharePoint architecture, definining portal taxonomies and physical deployment topologies/architecture, development and integration opportunities through Strategy Briefings and Architecture Design Sessions as well as "real world" implementation through Proof of Concept engagements to demonstrate the capabilties of a "live" SharePoint solution.  It's certainly great to see these getting packaged into a set of service offerings that we can make more widely available to our customers and partners.

And speaking of partners, this program is jointly managed by our partner ecosystem as well as Microsoft Consulting Services which together provides proven business and technical expertise in architecting/deploying SharePoint-based solutions for small, medium, and large organizations alike.

To learn more about the SDPS program and what it can do for you, head over to the SDPS website.  Microsoft Partners having strong competency in the Microsoft Office System stack are encouraged to sign up and participate in this growing community.

Zach Rosenfield (a Program Manager on the SharePoint Team) posted an announcment introducing the SharePoint Administration Toolkit.  This promises to be a great resource for administering your MOSS and WSS v3.0 deployments.  The initial version of the toolkit contains a couple of useful administrative tools, including the Batch Manager, which allows you to schedule bulk operations against site collections in a SharePoint farm, and a new command to the STSADM command-line utility called "updatealert" which will refresh all alert URLs in a specific site collection, which is important if you change the URL of a web application or after an upgrade.  A full whitepaper describing the toolkit can be found here.

Check out Zach's post of you want to have a good understanding of what the toolkit addresses and the features it contains.  The toolkit is available for download for both x86 and x64 SharePoint deployment configurations.

Enjoy!  I know I will! :-)

Microsoft has recently released a set of lectures and whitepapers on advanced topics around Office SharePoint Server 2007.  Below is a description (taken from the TechNet website) of topics and links.

Over on the SharePoint Team Blog is a good post citing resources related to deployments of MOSS/WSS on Windows Server 2008.  With the pending launch of the next release of Windows Server, it's important to know the impacts it has on deploying SharePoint Products & Technologies within your organization.  The resources cited in the post cover the following areas:

• WSS deployment on Windows Server 2008
• MOSS deployment on Windows Server 2008
• Upgrading from Windows Server 2003 to Windows Server 2008 with existing SharePoint deployments
• SQL Server 2008 and SharePoint deployments

Check out these resources if you're planning on deploying MOSS/WSS on Windows Server 2008 or want to understand more about the process.  As we near launch of Windows Server 2008, you'll start seeing even more resources around this very topic.