【文件属性】：
文件名称：微软SOA三步曲-微软SOA平台体系架构介绍
文件大小：19.58MB
文件格式：PPT
更新时间：2021-04-22 19:47:41
SOA，平台体系架构
微软SOA三步曲
1.凿山开渠
Data
Legacy
LOB
Packaged
Apps
Trading
Partners
Data
遗留系统
LOB
Packaged
Apps
Trading
Partners
*
© 2006 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.
*
Based upon this customer experience, we’ve tried to distill some of the lessons learned and keys to success.
First, as mentioned before, it’s critical to begin with grounding in your business drivers – SOA is a means to an end, not the goal. Many customers who viewed this as a big infrastructure investment project have put a lot of time and $$ into building layer after layer of the stack, meanwhile the business is changing more rapidly. Continuously changing business needs often get out of synch with long infrastructure efforts. The lack of Business and IT alignment can prevent SOA from delivering on it’s early promises.
In contrast, the customers we’ve seen be highly successful thru what we call a “real-world” approach, which departs from the industry norm of applying a high-risk, heavy, “top-down” strategy to SOA implementations that starts with major enterprise wide infrastructure investments that often fail to show results in a relevant timeframe or offer a compelling return on investment. Instead, the “real-world” approach to SOA advocated by Microsoft and practiced in successful customer SOA deployments relies on achieving rapid success around a focused business problem, which can result in broader SOA implementations.
Purely bottoms-up doesn’t work either – this can result in unmanaged chaos. Instead we see a successful model that we call “middle-out” – which begins with the business drivers and vision to set clear direction and priorities, but then takes multiple iterative steps to build out slices of end to end capability with each iteratiion delivering a new dynamic app back to the business to drive business return.
Now, we’re going to walk thru an actual example and discuss how you can put this into action. We see three common steps to any iterative SOA project entails. We’re going to drill into what a typical iteration of a project might look like.