EMEA Jürgen Pfeifer Architect, MCA Microsoft EMEA HQ http://blogs.msdn.com/juergenp SaaS in the Enterprise
EMEA
Jürgen Pfeifer
Architect, MCA
Microsoft EMEA HQ
http://blogs.msdn.com/juergenp
SaaS in the Enterprise
EMEA
WHY SAAS: LANDSCAPE AND
VALUE PROPOSITION TO THE
ENTERPRISE
EMEA
Context: “SaaS ecosystem”
EMEA
SaaS Impacts the Entire Consumption Cycle : In particular in the L.O.B. application space
Purchase
From:
Long Eval Process
To:
Try before you buy
Deployment
From:
Customization
To:
Configuration
Management
From:
Reliance on internal IT
To:
SLAs
Enterprise
EMEA
Value Prop
Hardware Cost
at Provider
People Cost
at Provider
Economy
of scale
EMEA
PRACTICAL
CONSIDERATIONS
EMEA
Considerations for embracing SaaS
EMEA
On Premise or in the “Cloud” ?
TECHNICAL
POLITICAL
FINANCIAL
LEGAL
EMEA
Examples of considerations
Examples T F L P
Boss said so x
Data security x x
Regulatory requirements x x
Required features/solution not available out there x
Business differentiator/core assets x
Requires deep integration with in house systems x
No incentive to optimize – what‟s the ROI to migrate? x
Unique SLA requirements x
Availability of credible SaaS providers x x
EMEA
Identity management
Need to cater for multi-tiered authentication and
authorisation models
Each client needs administrators / “super users” and regular users
Integration with enterprise identity management systems
Need to provide single sign-on from within the enterprise to SaaS
application(s)
Extend user provisioning process from enterprise into SaaS domains
Access to audit logs generated by SaaS application(s)
Consolidated reporting for compliance, etc
EMEA
Management integration
A chain is only as strong as its weakest link!
But in a world of SaaS what you care about is much broader
than what you can control directly
Need to be able to gain insight into operational health and
performance of SaaS applications
Benchmark against SLAs
Need to be able to integrate own systems management
information with information emitted from SaaS providers
What happens if your systems management environment uncovers a
problem with the SaaS system? Integration needs to be two-way
EMEA
Data ownership
Cultural issues
Concern about and fear of loss of control
Compliance / Security
Legal/regulatory issues e.g. data privacy limit options to host data externally or impose additional constraints e.g. testing using live data
Need to extend risk management and security strategies to the SaaS provider
Compliance demands end-to-end controls – but one end may be in the SaaS provider
Backup/recovery, disaster recovery
Data protection approaches must extend to externally hosted data
Disaster recovery must incorporate the SaaS solution e.g. can a disaster recovery site still connect? Is the data accessible?
EMEA
Now that you’ve decided on SaaS
Not all CRM SaaS are created equal.
Due diligence check list:
Data security standards
SLA guarantees – also check what action is promised
when SLA is violated.
Provider migration strategy: Availability of data and code
escrow services
Compliance with vertical regulations
In house integration requirements
Composition features: Web services interfaces
Additional reporting services on hosted data (to support
ongoing BI activities)
EMEA
SOA AND SAAS
EMEA
What is SOA?
Service Orientation:
Sets of architecture principles and design
patterns for delivering application architecture
that promotes agile and flexible reuse of IT
capabilities.
SOA:
A design artifact that represents an IT
architecture as a result of applying SO principles.
EMEA
SOA and SaaS
How SOA can help prepare enterprises for adopting
SaaS:
SOA Re-evaluate and re-factor technology capabilities
needed to deliver business. Capabilities = services
Adoption of standard-based technology helps enterprises
be more agile in adopting and switching capabilities.
Decouple services from processes. Loose coupling
enable new processes to be defined and reuse services.
What SOA will not do:
Help enterprise decide what is core and what is not core.
Core can refer to both data and processes.
EMEA
IMPACT ON YOUR
ARCHITECTURE
EMEA
Integration
EMEA
Composition
EMEA
Observations on Successful Enterprises
Companies who are able to do the following are
highly successful:
Harnessing and correlating the knowledge of collective
data
Specialization: how we do things -> lower cost, better
quality
Translating into technology capabilities:
Data integration
Synthesizing and collecting business information
Filtering noise from value
Composite applications
Better task flow
Better information flow
EMEA
Extending Enterprise SOA
Off-premise services
Integration + Composition Platform
On Premise Services
Internal
Edge
Cloud
EMEA
The role of the „EDGE“
SaaS is just one new way to use the „WEB as
a place“
Your external facing WEB functions need to
meet future expectations of your customers
and partners
The „Web 2.0“ wave
Your internal users expect that their own IT
enables this new world of work
e.g. Rich Content, Discovery (Search),
Collaboration
EMEA
Users & Experiences
The center of gravity shifts back to the User
It is the age of access
The experience economy
Wisdom of crowds
Democratization, of innovation, of content,
community and commerce
EMEA
24
Drivers
Business
Social
Technical
Technological
EMEA
Business Drivers
Changing business models (“Long-tail”)
Monetization
Free / indirect / bundling
Ad based revenue
Transaction based pricing
Subscription
Mini / micro transactions
Long tail
Business aggregation
Consumer to enterprise movement
EMEA
Social Drivers
Changing social models (“Gen U”)
User generated content
Power of numbers
Search and discovery
Community
“Folksonomies”
Personalization and responsiveness
Rich content (voice / image / video)
Ranking / rating
EMEA
Technical Drivers
Software + Services (“Live” era)
High levels of bandwidth and connectivity
Edge power (phone, ipod, PC)
Peer to peer
Mesh networks
Instant deployment / permanent beta
Rich content support (ipod, MP4, VOIP)
Lightweight tools
Channel filtering and aggregation
Application aggregation (mashups)
Services based
EMEA
Technologies
Lightweight technologies
REST
AJAX / Atlas
RSS / SSE
ROR
Wikis
IM / Bots
EMEA
Service-oriented architecture
An architectural style
Client/server, distributed objects, service-orientation
Evolution from the local (objects) to the network
(services)
Principles and patterns
Web services enable „intrinsic‟ interoperability
Facilitates „agility‟
Exploit new business opportunities and changing business
requirements
Means to an end
“I don‟t care how good your architecture is – what business
value are you creating?”
(I will confess that I don‟t buy the reuse argument)
EMEA
Service-oriented architecture
Enterprise-wide SOA
Service model
An approach to factoring, integrating, and managing
an organization's technology portfolio that employs
the service model as the basis for developing and
operating distributed business systems (yes, you can
do this using DCOM too )
Shared services
Security, management, metering, billing …
(I will confess that I am skeptical of Enterprise-
wide SOA)
EMEA
SOA / ESB Characteristics
Enterprise model
Centralized
Rigorous
Control
Server based
Managed
Standardized
„Slower‟ rate of change
SOAP based
EMEA
EDGE Definition
Provider and consumer model
Provider edge: Enterprises / SOA
Consumer edge: Consumers / Web 2.0
Is Web 2.0 the global SOA?
No they are two Edges
We need an architecture which covers both
EMEA
EDGE Characteristics
Async. / SOAPAsync. / RESTCommunication
Small (servers)Very LargeNo of types of devices
Enterprise EdgeConsumer Edge
SOA/ESBP2P/Web 2.0Name
CentralizedDecentralizedControl
LargeHugeTotal Demand
SlowFast Rate of change
LargeHugeTotal Power
MediumIn the web 2.0 cloudConnectivity
LargeVery LargeNo of devices
ManagedUnmanagedOrganization
EMEA
EDGE Common Capabilities
Relationship management
Rich content
Collaboration
Discovery
EMEA
EDGE Architecture
Web 2.0
SOA
Relationship
Management
Rich
ContentCollaboration Discovery
EMEA
EDGE Architecture
Web 2.0
SOA
Relationship
Management
Identity management
Friends, Family, Group management
Access management
Personalization
Tribes and “Folksonomies”
EMEA
EDGE Architecture
Web 2.0
SOA
Rich
Content
Video
TV
Image
Audio
Geo
Movie
EMEA
EDGE Architecture
Web 2.0
SOA
Collaboration
Blogs
Wikis
IM
Discussion boards
Conferencing (audio, video)
Back channeling
Bots
Wikipedia
EMEA
EDGE Architecture
Web 2.0
SOA
Discovery
Search
Tagging
Ranking and ratingClouding
EMEA
EDGE Architecture
Web 2.0
SOA
Relationship
Management
Rich
ContentCollaboration Discovery
EMEA
EDGE Architecture
Relationship
Management
Rich
ContentCollaboration Discovery
Interaction/
Composite
Application
Services/
Messaging
Workflow/
Process
Identity &
Access
Management
Federated
Data
EMEA
Patterns on the EDGE
Peer to peer (XBox Live, Napster, Skype)
Centralized (MSN Spaces, Google)
Asynchronous (Fremont, Flickr,
Housingmaps)
Hybrid
…
EMEA
People
Relationships Customers
Products/ServicesOperations
EMEA
Software Architecture at the EDGE
Web 2.0 SOAPut the User back into SOA
EMEA
Software Architecture at the EDGE
Web 2.0 SOAUser/Experiences
Architecture
© 2006 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS SUMMARY.