Upload
paulfallon
View
1.827
Download
0
Tags:
Embed Size (px)
DESCRIPTION
Citation preview
Paul FallonCTODot Net Soluti onsPaul.Fallon@DotNetSoluti ons.co.ukwww.dotnetsoluti ons.co.uk
What are the technical challenges when trying to integrate Cloud applications with existing architectures and legacy systems?
The Cloud Circle Forum
Case Study: The Body Shop Customer Loyalty Card ProgramAleksandar [email protected]
• No one ‘Cloud platform’ exists; meaning the specific migration, support, cost and capacity issues vary from vendor to vendor
• How do you integrate your legacy systems; for example, your email exchange with your Blackberry servers and Google Apps? How do you mix email functionality?
• What do your current software licences say? What about interoperability concerns?
• What are the ‘legacy to Cloud’ migration tools and bridging technologies that can connect internal IT systems with the Cloud in a secure and managed way?
• Will the adoption of Cloud increase the need for Master Data Management?
• What are the governance policies that need to be set up to enable integration to be managed effectively?
• How do you retrieve or migrate your data back to the data centre or between Cloud suppliers seamlessly
Topics and Questions to be covered
Agenda
Platform Continuum
• Bring your own machines, connectivity, software, etc.
• Complete control• Complete
responsibility• Static capabilities• Upfront capital costs
for the infrastructure
• Renting machines, connectivity, software
• Less control• Fewer
responsibilities• Lower capital costs • More flexible• Pay for fixed
capacity, even if idle
• Shared, multi-tenant infrastructure
• Virtualized & dynamic
• Scalable & available• Abstracted from the
infrastructure• Higher-level services• Pay as you go
On-PremisesServers
Hosted Servers
Cloud Platform
Three Layers of Cloud Computing
Software as a Service (SaaS)Finished applications that you rent and customize
Platform as a Service (PaaS)Developer platform that abstracts the infrastructure, OS and
middleware to drive developer productivity
Infrastructure as a Service (IaaS)Deployment platform that abstracts the physical infrastructure
SDKS o f t w a r e D e v e l o p m e n t K i t
Traditional IT
Storage
Servers
Networking
O/S
Middleware
Virtualization
Data
Applications
Runtime
You m
anag
e
Platform(as a
Service)M
an
ag
ed b
y v
en
dor
You m
anag
e
Storage
Servers
Networking
O/S
Middleware
Virtualization
Applications
Runtime
Data
Software(as a
Service)
Man
ag
ed b
y v
en
dor
Storage
Servers
Networking
O/S
Middleware
Virtualization
Applications
Runtime
Data
The Benefits of the Cloud
Infrastructure
(as a Service)
Storage
Servers
Networking
Middleware
Virtualization
Data
Applications
Runtime
Man
ag
ed b
y v
en
dor
You m
anag
e
O/S
Summary of Vendor Emphasis Provider vs Enabler
IaaS
PaaS
SaaS
Public Services
Private Services
Amazon
Salesforce.com
Microsoft
IBM
VMWare
Oracle
SAP
Cisco
Significant
None
Note: This is not an evaluation of capabilities, but rather of emphasis
Source: Garner Nov. 2010
Company A
Owner Company Company Provider Provider Provider
Operator Company Provider Provider Provider Provider
Service Access
Closed (Enterprise)
Closed (Enterprise)
Closed (Enterprise)
Limited Group
(Community)
Open
Level of Control
Full High High Low None
Custom Private Cloud
Virtual Private Cloud
Community Private Cloud
PublicCloud
Company A
Com
pany B
Com
pany D
Company A
Com
pany C
Managed Private Cloud
Com
pany B
Com
pany D
Com
pany C
Closed Private Open Public
Public to Private Services Spectrum
Com
pany A
Use
r 123
Cloud Computing
Service Orientation (SOA)
Enterprise Architectu
re
Standardized Service Contracts
Abstraction
Autonomy
Composability
Discoverability
Formal Contract
Loose Coupling
Reusability
Statelessness
Business Architecture
Application Architecture
Data Architecture
Technical Architecture
Governance
Policy
On-Demand Self Service
Ubiquitous Network Access
Resource Pooling
Rapid Elasticity
Pay-per-use
Services Driven
Cloud Computing Integration Scenarios
The Cloud
ENTERPRISE
DEDICATED CLOUD
PUBLIC CLOUD
PRIVATE CLOUD
Secure CloudFederation
INTERNAL IT
PUBLISH TO CLOUD
OR ENTERPRISE
Secure Cloud Federation
Cloud On-Premises
Data Synchronization
Application-layer Connectivity &
Messaging
Secure Network Connectivity
Security
• Powers movement of data
• Cloud Cloud
• On-Premises Cloud
• Getting data where you need it• Sync Cloud DB to Cloud DB
• Sync On-Premises DB to Cloud DB
• Sync offline apps to Cloud DB
• Enable geo-replication of data
Data Syncronisation
Sync
DB
Data Syncronisation – Example Use Cases•Move workloads in stages preserving existing infrastructure• Move part of the application and sync its data
•Meet compliance and regulations• Control data synchronized off-premises
• Enable scale-out read or read/write• Multiple synchronized databases for scalability
• Preserve data – geo replication of data
• Enable new scenarios• Spanning enterprise, cloud and remote offices/retail stores
Application Layer Connectivity & Messaging
• Extends reach of applications securely through the cloud
• Enables multi-tenant apps to integrate with tenants’ on-premises services
• Securely integrates partners outside of org boundaries
• Extends reach of on-premises web services layer
• Enables leveraging cloud quickly without having to rewrite apps
Service Bus
Send Receive
App 1 App 2
Receive Send
• Connectivity – patterns for integrating apps• Service Remoting – Extend services to the cloud• Cloud Eventing – Distribute event notifications to remote
listeners via the cloud• Protocol Tunneling – Interconnect distributed applications that
are not web services
• Messaging – patterns for building scalable apps• Load Leveling – Mediate message flows between components
with different send/receive rates• Loosely Connected Clients – Buffer messages for asynchronous
retrieval by remote clients
Service Bus – Usage Patterns
• Service location and discovery• Simple registry, endpoint naming and discovery
• Access via lightweight ATOM protocols from any platform
• Cloud-based communications relay• Allows bridging across NATs and Firewalls
• Claims-based access control with identity federation and rules
• Standards based HTTP or High Performance TCP
• Cloud-based messaging service• Message buffers accessible via a simple REST API
• BizTalk Server 2010 (AppFabric Connect)• Service Bus plus BizTalk 2010 to connect to on-premises legacy
systems
Service Bus – Core Capabilities
•Federated Identity
and Access Control
• .NET Windows Identity Foundation• WS-Federation, WS-Security,
WS-Trust protocols
•ADFS2• On-premises server
•Access Control• Identity federation service
Security
SecurityFederated Identity and Access Control
Virtualizing the Network
PUBLIC CLOUD
ENTERPRISE
PRIVATE CLOUD DEDICATED CLOUD
Secure CloudFederation
VIRTUAL NETWORK OVERLAY
Cloud Network
• Secure network connectivity between on-premises and cloud• Supports standard IP
protocols
• Enables hybrid apps access to on-premises servers
• Allows remote administration of Cloud apps
• e.g. Windows Azure Connect
Windows Azure Connect
Enterprise
Cloud
Windows Azure Connect – Example Use Cases
Windows Azure enterprise apps that require connectivity to on-premises SQL Server• Migrate apps without requiring changes or relocating on-
premises resources to be internet accessible
Windows Azure app domain-joined to on-premises Active Directory • Control access to Windows Azure apps based on existing
Active Directory accounts and groups
Remote administration and trouble-shooting of Windows Azure apps• Remote PowerShell to access Windows Azure role instances
Loyalty/CRM Program Pilot Implementati on
The Body Shop
Customer Case Study
Key Criteria for evaluating a SaaS/Cloud Service
• SaaS Solution Functionality
• SaaS Solution Pricing Terms and Conditions
• The availability (uptime) maintained by the SaaS provider
• The system response times maintained by the SaaS provider
• The SaaS provider’s accountability for quality of service
• The SaaS solution’s security and privacy
• The SaaS solution’s backup and recovery capability
• The SaaS solution’s customization and personalization capabilities
• The SaaS solution’s integration capabilities
• The SaaS solution’s workflow capabilities
• The capability to access and analyze SaaS data for business purposes
• The SaaS provider’s responsiveness to support requests
• The SaaS provider’s responsiveness to requested enhancements and changes
• The ability to network or participate in a community of SaaS solution users
Why Dot Net Solutions?
A Microsoft ‘Poster-Child’ – leader in technology innovation
Microsoft Technology Centre alliance partner
Community work – Edge user group & Cloud Evening
Pragmatism – build on existing solutions wherever possible
Partnership approach – engaging with the best
Dot Net SolutionsSoftware That Gets You Noticed
Summary
Q&A