惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

月光博客
月光博客
C
Check Point Blog
J
Java Code Geeks
腾讯CDC
Apple Machine Learning Research
Apple Machine Learning Research
宝玉的分享
宝玉的分享
Microsoft Azure Blog
Microsoft Azure Blog
WordPress大学
WordPress大学
量子位
Google DeepMind News
Google DeepMind News
I
InfoQ
The GitHub Blog
The GitHub Blog
aimingoo的专栏
aimingoo的专栏
N
Netflix TechBlog - Medium
Hugging Face - Blog
Hugging Face - Blog
博客园 - Franky
V
V2EX
Blog — PlanetScale
Blog — PlanetScale
T
The Blog of Author Tim Ferriss
小众软件
小众软件
博客园_首页
人人都是产品经理
人人都是产品经理
博客园 - 聂微东
IT之家
IT之家

博客园 - upzone

FTP Handler cannot be hosted in x64 Host instance Next Release of BizTalk Server: BizTalk Server 2010 R2 Passed MS BI Certification: 70-448 Passed new BizTalk Certification: 70-595 OLAP Architectures Comparison (ROLAP, MOLAP, HOLAP) 远程桌面访问Matlab的方法 FW: BIZTALK: Cannot perform encryption or decryption because the secret is not available from the master secret server 401 Unauthorized when call WCF in BizTalk,The authentication header received from the server was 'Negotiate,NTLM' - upzone Matlab first Prog. Visual Studio 2008: Install New Project Template SQL Server 兼容模式 FW: HTTP错误500显示具体的出错信息的方法 XmlSerialize error: There was an error generating the XML document. 装了Visual Studio 2010 后 Enterprise Single Sign-On 无法启动. Javascript 实现延迟跳转 - upzone - 博客园 Issue when try to get select count using Linq to SQL 六一,外公走了 FW: MOSS SSP Failed to provision - No running instances of Shared Services Provider provisioning TFS Build Notification: TFS 30063, you are not authorized to access the tfs
FW: BizTalk's furture
upzone · 2011-06-23 · via 博客园 - upzone

BizTalk’s future

With Microsoft’s push to the cloud people are publicly wondering about the amount of R&D investments being made in “traditional” on-premiss server software. Microsoft is making a big bet on cloud computing and they *will* succeed. Looking at BizTalk Server specifically, and Microsoft integration middleware in general I can tell you this:

In the past couple of years, Microsoft faced three major hurdles in the adoption of BizTalk Server:

1. Low latency challenges. This prohibited BizTalk being used in people facing applications.

2. .Net developers

3. The “two workflow engines” story

The first is commonly known. Until BizTalk 2010 you had to go into the Management Database to tweak some settings in order to accomplish lower latency scenarios. It still meant a minimum of 50ms for every persistence point, but for most scenarios it was okay. This could however not be combined with high throughput scenarios. Until BizTalk 2010, where these tuning settings can now be performed at the host and host instance level providing for combinations of low latency and high throughput solutions. But still…. every message goes at least once to the MessagBox database…

The second is probably less commonly known, but it is a fact that the “.Net developer” is the greatest BizTalk Server competitor. Why buy this stuff if you can build it yourself?

The third is also more and more known; why do we have two separate technologies and engines for handling human (WF) and system workflows (XLANG).

Together with the push to the cloud, this has resulted in some smart people at Microsoft coming up with a new architecture to make all of the above possible and satisfy everyone: one integration middleware architecture that enables development, deployment and management of integration solutions with one set of tools and which can be deployed in the Cloud and on-premises (Server or Appliance).

Watch for some cool stuff being released in the coming period. Some of it already has been released, such as this week’s CTP release of composite apps in Azure.

It will probably take them a couple of years until this all proves to work out well, but I’m confident they’ll manage. And for us integration specialists it will become better and better, because integration won’t go away and the architecture and tools will help us architect, design and build better integration solutions and at the same time bring new possibilities thanks to the cloud. This will be a real paradigm shift!

Cheers! Gijs

FW:

http://www.indafield.com/BizTalkNotes/2011/06/22/biztalks-future/