24 April 2007

"BizTalk Services" ISB debuts

This just in.... Microsoft has just released a Community Technology Preview (CTP) of BizTalk Services, a set of hosted services delivered via the Internet to help developers rapidly build and run composite applications at internet scale.  At it's core, it is an Internet Service Bus.

With platform technologies including Windows Server, the .NET Framework, BizTalk Server, and other so on, Microsoft has long been dedicated to delivering ever-broader application platform value to businesses that want to be able to buy+build+integrate their systems. The “BizTalk Services” ISB extends and complements the existing Microsoft platform to further advance the capability and productivity available to those businesses.

"BizTalk Services” is easily programmed through the familiar .NET Framework v3.0 and Visual Studio. In addition, the “BizTalk Services” capability is accessible through standard Internet and WS-* protocols making them fully interoperable with existing IT investments, and easy to use from a wide range of platforms.

Dino sez, check it out.

Oh, also, some other blogging attention: 

eWeek did a story, too

Filed under: , , ,
 

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

# BizTalk Services said:

PingBack from http://www.decatec.it/blogs/2007/04/23/BizTalk+Services.aspx

25 April 07 at 11:13 AM
# BizTalk Server Team Blog said:

Yesterday, our division went live with the Community Technology Preview (CTP) release of BizTalk Services

26 April 07 at 1:55 AM
# Gerald Beuchelt said:

Just a quick question, as you were filling this under "Interop[Java]":

As far as I can see, BizTalk Services defines a new transport, tagged "net.relay". What kind of protocols is this transport using? If we really want to get to an interoperable scenario (which I would find quite interesting), Microsoft would have to release the underlying protocols, yes?

Best,

Gerald

30 April 07 at 12:48 PM
# DotNetInterop said:

Yes, you are correct!  For full interop at that level, we'd need to document the underlying protocols.  a different option is to publish a reduced interface, available through http/get or something similar, that does not rely on binary transport and does not exploit the new biztalk services protocols.  (teaser: stay tuned for more on this, shortly!)

We're considering the best approach at this point.  Is it one option or the other?  Or both?  Or possibly something else?  We'd love your feedback on this.

11 May 07 at 7:28 PM
# All About Interop said:

With the unveiling of Project Astoria , we're seeing more and more "services in the sky" from Microsoft.

22 May 07 at 9:07 AM

Leave a Comment

Comment Policy: No HTML allowed. URIs and line breaks are converted automatically. Your e–mail address will not show up on any public page.

(required) 
(optional)
(required) 

  
Enter Code Here: Required
Page view tracker