Datacenter LOB web service LOB app Partner Mobile Device.
27
Intro to Windows Azure AppFabric Name Title Microsoft Corporation
-
Upload
bertram-brooks -
Category
Documents
-
view
222 -
download
4
Transcript of Datacenter LOB web service LOB app Partner Mobile Device.
Intro to Windows Azure AppFabric
NameTitleMicrosoft Corporation
Session Objectives
What is Windows Azure AppFabricHow is it used?Billing and PricingEnvironments
Challenges Today
How do you integrate with components outside your corporate network?How do you expose your software to users outside of your organization?
Can they use their existing identities?What about smaller, non-enterprise customers?
How do you control access to resources that are exposed?<the list goes on…>
Windows Azure AppFabric
A natural way to extend the reach of
existing services through the cloud
Leverage existing investments in SOA and EAI solutionsExtend the reach of on-premises web services layerEnable hybrid applicationsSecurity integrate with partners outside of the organizational boundaries
About Windows Azure AppFabric
Service BusConnectivity across network topologies
Access Control ServiceFederated, claims-based authorization for websites and web services
Enabling hybrid applications
Datacenter
LOB web
service
LOB app
Partner
Mobile Device
Enabling hybrid applications
Datacenter
LOB web
service
LOB app
Partner
Mobile Device
SB
ACS
Enabling hybrid applications
Datacenter
LOB web
service
LOB app
Partner
Mobile Device
SB
ACS
Enabling hybrid applications
Datacenter
LOB web
service
LOB app
Partner
Mobile Device
SB
ACS
Enabling hybrid applications
Datacenter
LOB web
service
LOB app
Partner
Mobile Device
SB
ACS
Service Bus
What is it?
Extension to the familiar WCF binding model
SOAP/HTTPSOAP/TCPHTTP
Simple HTTP APIs for Service Management
Service Registry (Atom Publishing Protocol)Message Buffer (REST)
Fully integrated with Access Control Service
Service Bus
Exchange messages between loosely coupled applicationsNetwork send/receive from any internet connected deviceTraverse NAT/FirewallMessage buffering for loosely connected applicationsFacilitate direct peer-to-peer connection
Send Receive
Service Bus
App 1 App 2
Receive
Send
Core Capabilities
Service location and discoverySimple registryAccess via lightweight ATOM protocols from any platformEndpoint naming and discovery
Cloud based messaging relayAllows bridging across NATs and FirewallsConnect apps without altering the network topologyNetwork Listen/Send from any Internet-connected deviceStandards based HTTP or High Performance TCPDirect connection functionality using NAT probing
Service Bus Patterns
Service RemotingExtend Services to the Cloud
EventingEvent Distribution; something happens, you get a notification
Protocol TunnelingInterconnect applications that are not Web Services
Service Bus
Access Control
Service Remoting
Sender Listener
Access Web Services across the InternetPublish services and communicate bi-directionally
Service Bus
Access Control
Eventing
Notify remote parties of eventsSender transmits information to listeners
Events are distributed unicast or multicast
Listener
Listener
Sender
Service Bus
Access Control
Sender Listener
Tunneling
Transport existing protocols over Service Bus
Protocol Bridge
Protocol Bridge
Access Control Service
Why an Access Control Service?
Federate identityLeveraging multiple identity providers per applicationADFS v2, Live ID, Facebook, Yahoo, Google, …
Identity abstractionEvolve past username/passwordLeverage claims-based identity
Access Control Service
YourService
2. Request token
(pass input claims)
4. Return token
(receive output claims)
5. Send messagewith token
0. Establish trust via key exchange
Customer
1. Define access control rules for an identity provider
3. Map input claims to output claims based on access control rules
How it works
6. Processtoken
Capabilities
ACS == claims-based access controlKey features
Open to all platformsSimple rules for mapping input to output claimsOAuth WRAP & SWTIntegrates with ADFS v2
All web services can take advantage of these capabilities with a single code base
Pricing & Environments
Billing and Pricing
Service BusIndividual @ $3.99 per connection-monthPack-based @ $1.99 per connection-month
Access ControlConsumption @ $1.99 per 100k transactions
BandwidthSame as Windows Azure
Environments
ProductionPaying customers, support, SLAs3 month release cadence<your-namespace>.servicebus.windows.netGeo-located
LabsFree, no support, no SLA~3 month release cadence<your-namespace>.servicebus.appfabriclabs.comAvailable for evaluation and prototyping
Takeaways
AppFabric provides a natural way to extend the reach of existing services through the cloudService Bus provides a topology agnostic message bus in the cloudAccess Control Service removes complex authentication and authorization rules from your application
© 2010 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.
