Quantcast



Docs


Blogs


Forums


Samples


Media


Labs


Resources

 




DevCentral > Weblogs > Lori MacVittie - Two Different Socks
 How Microsoft is bursting into the cloud with BizTalk
posted on Monday, October 06, 2008 3:29 AM

Darren Jefford has an excellent (and detailed with code examples) post Related Posts
regarding what could easily be categorized as cloudbursting with BizTalk workflows.

In a nutshell, Microsoft allows hosting of BizTalk activities in the cloud at BizTalk labs. Developers then integrate those cloud hosted activities into a BizTalk workflow (orchestration) by calling them as they would any other web-based service or hosted activity.

In doing so, Microsoft is essentially allowing developers to extend the compute capacity of their data centers by leveraging the much larger data centers maintained by Microsoft.

The Three "Itys" of Cloud Computing

Bursting the Cloud

Building a cloudbursting capable infrastructure

4 things you need in a cloud computing infrastructure
What is an activity?  
An activity is a discrete step in a business process (workflow). Activities range from calling a remote service to perform a task, e.g. calculating taxes, performing currency conversions, looking up inventory, to custom-defined services.

Activities are orchestrated together together a workflow in BizTalk using XOML (eXtensible Object Markup Language).

In other BPM (Business Process Management) solutions, activities are orchestrated using BPEL (Business Process Execution Language).

Both XOML and BPEL are XML-based markup languages used for orchestrating workflows.

BPEL is an industry standard; XOML is Microsoft's propriety solution.
biztalk-cloudbursting
      How Microsoft BizTalk workflows take advantage of cloud-based activities

While the first definitions of cloudbursting are focused on reactive capacity management, Microsoft appears to be taking a proactive approach to cloudbursting and capacity management. By encouraging developers to utilize the compute capacity of BizTalk labs up front during the design and development process, it alleviates the need to react hastily later when it becomes apparent that more compute resources are necessary for a specific workflow activity.

The concept remains the same: utilize the cloud for additional capacity when it is apparent your own data center can't handle the load and it is cost-prohibitive to invest in additional servers and infrastructure to increase capacity.

One can easily imagine that future offerings might include the ability of other organizations to subscribe to and use activities developed by third-parties, essentially offering yet another path to monetize the cloud.

Follow me on Twitter View Lori's profile on SlideShare AddThis Feed Button Bookmark and Share



Email This
  del.icio.us
      

Feedback


10/6/2008 10:15 AM
Gravatar In intresting blog but a little wrong in your terminology. Microsoft in their infinte 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 Comunication foundation. No it is true that we will/can be able to host our workflows in the cloud, and use the internet service bus but it ain'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 lanuage of BizTalk orchestrations.

After PDC this will become a lot clearer!

Andy James Member of the Microsoft Cloud Advisory Group
Andy James

10/6/2008 11:03 AM
Gravatar @Andy,

I really wasn't trying to imply that the services (BizTalk services) were BizTalk themselves, but that they were usable from within BizTalk, which is what the referenced article discusses. From within BizTalk they're referenced from within a CloudHTTPService activity, implying they are traditional HTTP-based web services residing in the cloud. Given that any web service should be accessible from any BPM engine, this really isn't new except that it's implying potential future services that might be shareable/monetizable, and utilizes the cloud in a proactive way to address capacity and execution.

However, as you point out, terminology being what it is, I can see how how it might appear as specifically a product of BizTalk and therefore a workflow. I guess being intimately familiar with BPM I failed to explain in more depth what it means to deploy an "activity" when really all that entails in this case is a deploying a web service which is not, technically, specific to BizTalk.

I'm looking forward to hearing even more after PDC.

Thanks,
Lori
Lori MacVittie
 Leave Feedback
Title  
Name  
Email
Url
Comments   
Please add 8 and 4 and type the answer here: