SOA and Cloud Computing

10
SOA and Cloud Computing David Chou [email protected] blogs.msdn.com/dachou

description

David Chou's presentation on SOA and Cloud Computing for Architects

Transcript of SOA and Cloud Computing

Page 1: SOA and Cloud Computing

SOA and Cloud Computing

David [email protected]

blogs.msdn.com/dachou

Page 2: SOA and Cloud Computing

State of SOA

>Perceptions• SOA = IT centralization/standardization• “SOA is dead” (Anne Thomas Manes, Burton Group; January

2009)

• Cloud computing will replace SOA

>Reality• SOA does not solve all enterprise IT issues• SOA is complex, and difficult• Core value of SOA is agility, but needs vary• SOA demands change, but organizational

resistance is often the biggest impediment• Need to focus on architecture, not technology

Page 3: SOA and Cloud Computing

SOA Manifesto

Service orientation is a paradigm that frames what you do. Service-oriented architecture (SOA) is a type of architecture

that results from applying service orientation.

We have been applying service orientation to help organizations consistently deliver sustainable business value, with increased agility

and cost effectiveness, in line with changing business needs.

Through our work we have come to prioritize:

Business value over technical strategy Strategic goals over project-specific benefits

Intrinsic interoperability over custom integration Shared services over specific-purpose implementations

Flexibility over optimization Evolutionary refinement over pursuit of initial perfection

That is, while we value the items on the right, we value the items on the left more.

http://www.soa-manifesto.org/

Page 4: SOA and Cloud Computing

SOA Principles

>Reuse

>Granularity / Modularity / Componentization

>Loose Coupling / Contractual Design

>Interoperability / Standards Compliance

>Abstraction / Encapsulation

>Composability

>Discoverability

>Manageability

Page 5: SOA and Cloud Computing

SOA Principles, Redux (for “Small SOA”)

>Reuse

>Granularity / Modularity / Componentization

>Loose Coupling / Contractual Design

>Interoperability / Standards Compliance

>Abstraction / Encapsulation

>Composability

>Discoverability

>Manageability

Page 6: SOA and Cloud Computing

SOA, Meet Cloud Computing

SO-Architecture> A different approach to

organize enterprise IT resources

> Governance> Management> Strategic framework

and planning> People and process

IT-as-a-Service> A different model to

leverage computing resources

> Service design> Higher-level abstraction> Tactical and incremental

implementation> Data and technology

Page 7: SOA and Cloud Computing

Some Considerations for the Cloud

> Cloud as an extension of enterprise SOA

> Resources beyond enterprise boundaries (“Intercloud”; networks without borders)

> Loose-coupling everywhere (in service contracts, data relationships, process dependencies, identity, communication models, performance expectations, change management processes, etc.)

> More trust needed (lower security requirements, virtual & shared infrastructure, multi-tenancy, Internet transit, etc.)

> Different fault zones/domains, criticality tiers (one big monolithic SOA vs. federated distributed SOA)

> New development efforts (instead of moving legacy applications into someone else’s data center)

Page 8: SOA and Cloud Computing

Web as a Platform“Intercloud” – an interconnected global “cloud of clouds”

Page 9: SOA and Cloud Computing

Emerging Trends

>De-perimeterization>Democratization of industries>Dynamic business models>Relationship networking core competencies>Shifting process centers of gravity>Plug-and-play IT architectures>Model-driven development

Page 10: SOA and Cloud Computing

[email protected]/dachou

Thank you

© 2009 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.