Get documents about "How to Start Real State Business
Description
How to Start Real State Business document sample
Document Sample
The SOA ROI Crisis…
“The Dark Side of SOA” “The Truth About SOA”
InformationWeek, September 4, CIO Magazine, June 15, 2006
2006
Loose
Scale
Coupling
Re-use
Challenge Details
Loose coupling • Messaging
• Autonomy
• Interoperability
• Service virtualization
Scale • Horizontal
• Elastic
• State management
• Long running processes
Re-use • Composition / Mash-ups
• Economics
• Integration
Challenge Details
Loose coupling • Messaging
• Autonomy
• Interoperability
• Service virtualization
Scale • Horizontal
• Elastic
• State management
• Long running processes
Re-use • Composition / Mash-ups
• Economics
• Integration
Challenge Details
Loose coupling
Scale • Global Distribution And
Deployment
• AuthN / AuthZ Across Boundaries
Re-use • Bridging On-Premise and Cloud
• Robust Connections Across NAT,
Protocol and Fireball Boundaries
Loose
Scale
Coupling
Re-use
Loose
Scale
Coupling
Re-use
Stateful State State Repository
Repository + State
Messaging
Users
Services Tier
Application Application
… Application
(ASP.Net /
Caching Access Caching Access Caching Access WCF)
Layer Layer Layer
Database Cloud Data Tier
Caching
Service
Caching
Service
Caching
Service
Cache Tier
Windows Azure
Service Instances
Loose
Scale
Coupling
Re-use
3rd Party
Consumer
Azure Queues or Service Bus
(REST / HTTP Interface)
Division of Roles into
Loosely Coupled Roles
Web Role Worker Role
Interoperable Service
Protocols: SOAP, REST,
JSON
Autonomous
Instances
AppFabric Service Bus Connectivity
Text
XML
Graphics
Binary Data Receive Receive
Streaming
Firewall
Send Send
Exchange messages between loosely
coupled, composite applications.
Direct Connection facilitated by
Application #1 Service Bus if that is best Application #2
connection mechanism.
Global Collection Pattern #1
• Multiple distributed endpoints publish a message up to their closest Azure DC
• Messages are collected and relayed to a central collection Azure DC
• Messages are used at the central DC, or relayed down to on-premises
Europe Region Asia Pacific Region North America Region
Messages are received by an
on-premise application
Messages from remote endpoints “call
home” to a single Windows Azure
collection point
Global Collection Pattern #2
• Multiple distributed endpoints publish a message up to a single Azure region
• Messages are used at the central DC, or relayed down to on-premises
Europe Region Asia Pacific Region North America Region
Multiple distributed end-point applications
“report up” to the single Azure data center
Messages are received by an
North Europe on-premise application
US North Central
Sub-region Sub-region
US South Central
Sub-region
Messages from the other Azure data
South East Asia centers “roll up” to a central collection
Sub-region point data center
Traditional Point-to-point On-Premise
Point-to-point with cloud ESB with cloud
CRM
Loose
Scale
Coupling
Re-use
Patterns:
Orchestration
Composite UI
Requires:
Composition Runtime
Message Brokers (Routing / Transformation)
Support for Compensation (WF/Biztalk)
Development Tools (Visual Studio)
Ownership Model
Supervising
View
Presenter
Model
Presentation
View Model
Model
Finding & Loading Modules
Module Loader
Building the Experience
<ItemsControl
RegionManager.RegionName= MyView view = …;
“DataRegion">
IRegion buySellRegion =
regionManager.Regions[ “BuySellRegion" ];
<ContentControl buySellRegion.Add( view );
RegionManager.RegionName=
“BuySellRegion” />
Region
Region
Region
Building the Experience
regionManager.RegisterViewType(
<ContentControl “BuySellRegion", typeof( BuySellView ) );
RegionManager.RegionName=
“BuySellRegion” />
Region
Region
Region
On-Premise Cloud
Loose coupling Windows Server AppFabric Windows Azure Platform
BizTalk Windows Azure AppFabric
Re-use BizTalk, BizTalk ESB, Mash-ups Windows Azure Platform
(Prism, Silverlight, WPF, AppFabric Service Bus
SharePoint)
Scale Windows Server AppFabric Windows Azure Platform
BizTalk
Related docs
Other docs by spx12209
