Software + Services: An Architect Perspective

1. Software + Services: An Architect Perspective • Gianpaolo Carraro • gianpc@microsoft.com http://blogs.msdn.com/gianpaolo

2. Agenda • What is S+S • Why are people interested in S+S • Architecture impact of S+S • (session #2 after the break) An S+S example

3. It seems that the future will be “cloudy” “Cloud” Software Internet “Cloud” Platforms “Cloud” UX

4. 70’s “Pendulum Syndrome” 80’s 90’s 00’s Centralised, Managed Democratised, Adaptable

5. FROM TO Software makes services better and services make software better.

6. From: All or Nothing To: Fine Control

7. “S+S World”

8. S+S Architecture Perspectives Monetize Build Consume Run

9. S+S Perspectives

10. Long Tail

11. S+S Common Pattern #1 • Client • Server • Service • Rich User Experiences • Disconnected experience • Smart Client • Office as UI • “Back end as a service” • Multitenancy vs. Isolation • Metadata Driven Customization • Performance • Self Service / Try before you buy • Taking advantage of • ‘cloud’ building blocks • Latency • SLAs

12. S+S Common Pattern #2: Attached Services • XBOX -> XBOX Live • Office -> Office Live Workspaces • Exchange -> Exchange Hosted Services • Leverage the installed based • New revenue streams • little re-architecting of original application

13. Garmin

14. S+S Perspectives

15. Value Added Services ISV “A” App ISV “B” App UI + Biz Logic UI + Biz Logic Business Services Business Services Billing Metering Billing Metering Operational Mgmt Operational Mgmt App Architecture App Architecture Caching Caching Logging Logging Exceptions Exceptions Profile Profile OS & Core Infrastructure Incident Escalation Fault Tolerance Database Infr. Tools Core Monitoring Network Services Storage Execution Security Operational Services Hardware Capacity Planning SLA Monitoring Servers Disks Network Datacenter

16. Value Added Services ISV “A” App ISV “B” App ISV “C” App UI + Biz Logic UI + Biz Logic UI + Biz Logic Business Services Branding Moneti-zation Metering Tenant Provisioning Timed SLA Remote Management Environments Application Architecture Logging Identity MT Data Access Exception Handing OS & Core Infrastructure Incident Escalation Fault Tolerance Database Infr. Tools Core Monitoring Network Services Storage Execution Security Operational Services Hardware Capacity Planning SLA Monitoring Servers Disks Network Datacenter

17. Global Foundation Services

18. S+S Perspectives

19. S+S Architecture: Consume • Integration Architecture • SSO • Unified Management • “Many to 1 consumption” • Composition Architecture • “enterprise mashups” Global Bank “Extended” SOA

20. Where do I run (deliver)? (usually) Lower Cost More Control On Premise “Cloud” • Considerations: • What is the SLA of “the cloud” • Core competencies vs. Commodity • Transparency in pricing and SLA • …

21. Intra-net S+S • Same concepts but within firewalls • Example: • eBanking system deployed in 7 countries • public sector: shared services

22. S+S Perspectives

23. 2 Sided Market Aggregator

24. S+S Architecture: Monetize