Microsoft unveiled a major release of Windows Azure on Thursday, June 7 at the “Meet Windows Azure” event. Windows Azure has been out for quite some time, but some in the industry are describing this as Windows Azure 2.0. The amount of new functionality is really impressive and is the culmination of more than a year of work. If you were unable to attend, the full event was recorded which can be seen at http://www.meetwindowsazure.com/Conversations.
If you do not already have an account to access Windows Azure, you can sign up for a free 90-day preview at http://www.windowsazure.com/.
Once you obtain an account or if you already have a Windows Azure account, open up the Management Portal and select “Visit the Preview Portal” from the menu on the bottom of the page. This will allow you to toggle between the preview portal and the current portal while the new features are fully enabled.
I’m still digging through the new features and digesting all the possibilities, but I really like what I see so far.
Picking up where we left off in the Service Bus Introduction, this post will walk through a Relayed Messaging sample in order to highlight how the AppFabric Service Bus could be utilized to build Hybrid applications. In addition to the basic sample, I will also demonstrate how to provision a BizTalk Server 2010 Receive Location on the Service Bus.
Before I publish the next post on Relayed Messaging, I thought I would take this opportunity to share some lessons learned yesterday about the AppFabric Service Bus billing. Continue reading
I recently had the honor of delivering a presentation entitled “Build Hybrid Applications Using the Azure AppFabric Service Bus” at the Richmond and Philly.NET Code Camps. Virtually no one in either of the sessions had any previous experience with Windows Azure or the components of the AppFabric. In this series of blog posts, I will expand upon the presentation in an effort to introduce the AppFabric and take a deeper dive into the code and practical application of the Service Bus messaging patterns.
Earlier this week I participated in a discussion thread on LinkedIn regarding the usage of the WCF SQL Adapter in BizTalk Server and I wanted to summarize some of my thoughts and the recommended best practices regarding this particular scenario.
The reports of my death are greatly exaggerated. ~Mark Twain (or BizTalk Server)
For the past 5 years or so, various technologists have been predicting or even proclaiming the untimely demise of Microsoft BizTalk Server. Usually these predictions come in the form of blog posts espousing the new hotness whether it was a new product from Microsoft or a competing product claiming it was a better middleware solution than BizTalk. Oddly enough, the chatter ramps up the loudest shortly after Microsoft releases a new CTP of technology X that may be tangentially related to an existing product like BizTalk. The problem with all of the proclamations is that they never seem to come from the Microsoft Product Development groups or BizTalk MVPs. I am not an MVP, but I do consider myself to be plugged in to what is happening with BizTalk. With that in mind, I would like to briefly take a look at the current state of BizTalk’s life and put an end to the urban legend.
In an effort to maintain control over the proliferation of application servers and data, many organizations have undertaken projects to consolidate and integrate systems. One of the first hurdles in undertaking an integration project is determining the most efficient integration technology. Unfortunately, just within the Microsoft stack, there are technologies that consistently cause confusion and are often misused. Continue reading