Geeks With Blogs

Connected Systems Chilled Out Blog Hanging stuff together in a meaningful way with some fun added

I have recently been invited to join the Microsoft Cloud Advisory group and have just spent the last week at an SDR getting to understand all the wonderful cloud stuff. Unfortunately I'm under NDA until PDC but it is looking good.

On the topic of the cloud and BizTalk I came across a blog by Lori MacVittie (

that really has got it all wrong. The blog talks about BizTalk activities in the cloud and orchestrations and on but has missed the point completely.

Microsoft in their infinite wisdom named their cloud messaging and workflow technologies BizTalk Services. In fact they have nothing to do with BizTalk!!! They are based on the Windows Workflow foundation and the Windows Communication foundation. No it is true that we will/can be able to host our workflow's in the cloud, and use the Internet service bus it isn't and never will be BizTalk. I cannot do transformations, having adapters and accelerators coming out my ears and the like and I will not/am not able to use BPEL in the cloud - the underlying language of BizTalk orchestrations.

After PDC this will become a lot clearer!


Technorati Tags: ,
Posted on Monday, October 6, 2008 5:21 AM BizTalk 2006 , BizTalk V.Next , Microsoft News | Back to top

Comments on this post: Head in the cloud

# re: Head in the cloud
Requesting Gravatar...
I replied to this same comment but to reiterate: I think you're right about the problem with naming. Orchestrations and workflow are executed in the data center, but services - whether cloud or elsewhere - can be executed anywhere.

Darren's example is clear - he is executing a service (a workflow/BPEL/BizTalk activity) in the cloud using a BizTalk CloudHTTPService. That the BizTalk services hosted in Microsoft's cloud are named as such may be irrelevant to BizTalk, but only in the sense that any web service should be accessible via BizTalk or any other BPM or a .NET application, for that matter.

Hosting "pieces" of a workflow in the cloud simply entails hosting a service in the cloud; the confusion between an activity and a service is part of the problem as BPM and SOA have clouded (pardon the pun) the issue.

Again, thanks for clarification on the BizTalk services and naming issue, I will be sure to be more clear about what it means to be a "BizTalk" service in the future, and am looking forward to hearing more of your revelations regarding Microsoft, BizTalk, and the cloud.

Left by Lori MacVittie on Oct 07, 2008 1:24 AM

Your comment:
 (will show your gravatar)

Copyright © BizTalk Visionary | Powered by: