Description

In the simplest definition, BizTalk Services simplifies application connectivity by extending WCF and providing a set of hosted services. John and Dennis quickly explain BizTalk Services by discussing the challenges with building applications today. Dennis
also shows four demos of BizTalk Services and then drops into Visual Studio along the way to show the programming model.

The Discussion

That is an impressive demo!!! The potential of this is very far reaching specially in the SOA space.

Anyway I have some questions if that’s ok, and they are …

So what is the performance like?How far can I scale this?Can I get this to work with (W)WF? Can I do async or long running communications with this technology?Have you tried connecting this to Java and other non-Microsoft technologies?Isn’t calling this technology ‘Biztalk Connectivity Services’ going to get it confused with the full Biztalk product? Specially if there is no migration strategy from one to the other?

I’m pretty excited about this … and I have a 100 more questions but that’s enough to be getting on with for now.

BizBusCFBus.NetFX Discussion ServicesParleyCakeCom ... because it's as simple as

Gosh, I really hope this is in Orcas! My reasoning is because if it's there Devs will use it. If it's not many Dev's won't know of it's existence and try and write there own. If it's intention is to be free then why not bundle it in, hey it could even be another
selling point (like Orcas needed any more!)

As John and Dennis indicated, the project is nascent at this point. Given that it is still in CTP form, it can't be rolled into the Orcas release (Orcas in Beta1, moving to Beta2).

Have you played with the Services yet? If not, I encourage you to check them out. If you have suggestions about the product, you can either provide feedback here or on the
http://labs.biztalk.net site.

I am composing a reply to your other post as well - have to check a fact first...

There's really no architectural blockage that would stop us from eventually keeping an event cache around up in the cloud. As Justin wrote, the ISB is nascent, but you can let your imagination go and think of what the potential is.

In relation to occasionaly connected clients, because ISB crosses over the internet it is a good point to raise the question of occasionaly connected clients and services.
WS-Discovery could apply quite nicely. Standardized Bye/Hello and Probe/Resolve messages could offer a WS* compliant solution to provide presence awareness and discovery and as well a s ensuring interoperability.