Your SlideShare is downloading. ×
0
Soa 101
Soa 101
Soa 101
Soa 101
Soa 101
Soa 101
Soa 101
Soa 101
Soa 101
Soa 101
Soa 101
Soa 101
Soa 101
Soa 101
Soa 101
Soa 101
Soa 101
Soa 101
Soa 101
Soa 101
Soa 101
Soa 101
Soa 101
Soa 101
Soa 101
Soa 101
Soa 101
Soa 101
Soa 101
Soa 101
Soa 101
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Soa 101

1,743

Published on

Published in: Business, Technology
0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,743
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
86
Comments
0
Likes
3
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Transcript

    • 1. SOA 101 David S. Linthicum
    • 2. <ul><li>Blogs: </li></ul><ul><ul><li>eBizq.net “Linthicum Channel” </li></ul></ul><ul><ul><li>IT Toolbox “CEO’s Guide to SOA and Application Integration” </li></ul></ul><ul><ul><li>InfoWorld “Real World SOA” </li></ul></ul><ul><li>Weekly Podcast </li></ul><ul><ul><li>www.soaexpertpodcast.com </li></ul></ul><ul><li>New Gig </li></ul><ul><ul><li>CEO BRIDGEWERX </li></ul></ul><ul><li>New Book: 12 Steps to SOA </li></ul>
    • 3. SOA…What’s New Here?
    • 4. The Integration Challenge… <ul><li>The N-squared Integration Problem: </li></ul>
    • 5. …Made Worse by External Integration <ul><li>70% of IT development budgets are spent on integrating different systems – ZapThink </li></ul>
    • 6. The “Rat’s Nest” Architecture FBT PAY G NTS TRDS Client Customs RRE IPS Integrated A/C Refunds RBA Def Payments Excise CR PKI ECI ADD AWA ELS Client Staff Remote Staff TAX AGENTS GCI Call Centers WOC CCD TASS Staff Phone Compliance Staff BOA Ref material Bus. Intel NTS A/c BEP CDCC CWMS BANK DDDR 1 Data……. Penalty Business IVR 1
    • 7. IT: Fulfilling Business Requirements <ul><li>Business Requirements </li></ul><ul><li>Service Customers </li></ul><ul><li>Manage Operations </li></ul><ul><li>Increase Worker Productivity </li></ul><ul><li>Communicate with market </li></ul><ul><li>Ensure reliable and secure operations </li></ul><ul><li>Develop new products and services </li></ul><ul><li>Respond to new business drivers </li></ul><ul><li>IT Capabilities </li></ul><ul><li>Implement CRM Systems </li></ul><ul><li>Implement ERP Systems </li></ul><ul><li>Manage desktop environments </li></ul><ul><li>Manage server environments </li></ul><ul><li>Manage email systems and web sites </li></ul><ul><li>Manage network and storage operations </li></ul><ul><li>Develop applications </li></ul>
    • 8. However, it rarely works that way… <ul><li>Requirements change </li></ul><ul><li>Interpretations often inaccurate or limited </li></ul><ul><li>Lengthy development cycles impervious to change </li></ul><ul><li>Implementations “cast in concrete” </li></ul>Result: IT that places limitations on Business
    • 9. What is a Service-Oriented Architecture? <ul><li>Access software via Services that are easy to find and connect to </li></ul><ul><li>Web Services provide a s tandard way of building and accessing Services </li></ul><ul><li>Developers &amp; integrators can build applications out of Services </li></ul>
    • 10. Application Integration Solution Types
    • 11. The High Level Integration Stack
    • 12. Logic Transformation Formatting Data Logic User Interface Data
    • 13. &nbsp;
    • 14. Service Oriented Application Integration <ul><li>Service integration to create a composite application </li></ul><ul><li>Sharing business logic </li></ul><ul><li>Sharing code </li></ul><ul><li>Sharing processing </li></ul><ul><ul><li>Shared programs </li></ul></ul><ul><ul><li>Shared transactions </li></ul></ul><ul><ul><li>Shared objects </li></ul></ul>
    • 15. Application Integration is Evolving Business Process Control (Process Integration Oriented)
    • 16. Contrasting Three Forms of Integration <ul><li>Loosely or tightly coupled integration </li></ul><ul><li>Single application </li></ul><ul><li>Synchronous dominates </li></ul><ul><li>Request/reply </li></ul><ul><li>Complex abstraction of business rules </li></ul><ul><li>Loosely coupled integration </li></ul><ul><li>Multiple applications </li></ul><ul><li>Can be either Asynchronous or Synchronous based </li></ul><ul><li>One-way and request/reply </li></ul><ul><li>Limited complexity in abstraction of business rules </li></ul><ul><li>Loosely coupled integration </li></ul><ul><li>Multiple applications </li></ul><ul><li>Asynchronous dominates </li></ul><ul><li>One-way </li></ul><ul><li>Simple abstraction of business rules </li></ul>Service Oriented Multi-step Process Data Consistency
    • 17. Multistep Process (Information-Oriented) Dominates… For Now
    • 18. Process Orchestration will Control SOA
    • 19. Composite Application
    • 20. Value of Services <ul><li>Limitations of information-oriented integration </li></ul><ul><ul><li>Limited visibility </li></ul></ul><ul><ul><li>Limited reuse </li></ul></ul><ul><ul><li>Latency </li></ul></ul><ul><li>Advantages of leveraging service-oriented integration </li></ul><ul><ul><li>Visibility at the information and the behavior levels </li></ul></ul><ul><ul><li>Reuse of services among trading partners </li></ul></ul><ul><ul><li>Real-time integration </li></ul></ul>
    • 21. The Economics of Integration
    • 22. The Economics of Integration
    • 23. The Economics of Integration
    • 24. The Economics of Integration
    • 25. The Economics of Integration
    • 26. Development model for SOA <ul><li>Integration tightly couples end-points </li></ul><ul><li>Interoperability considers each end point separately </li></ul><ul><ul><li>Producer: Provides service </li></ul></ul><ul><ul><li>Consumer: Consumes the service </li></ul></ul><ul><li>Producer/Consumers describe their interfaces and are then connected at run time (late binding) </li></ul><ul><li>Focus on agreement of business service interface </li></ul><ul><ul><li>Do not focus on operating system, implementation, etc…. </li></ul></ul>Producer Consumer SOA (Shared Services) Consumer Interface Producer Interface
    • 27. Gartner’s Architecture Application Domain Integration Domain Data Domain Point of Access Domain Business Architecture Business Architecture Patterns Business Relationship Grid Bricks Business Processes, Styles System Management Domain Security Domain Infrastructure Domain Information Architecture Technical Architecture
    • 28. Directions for SOA Three Levels of Web Service Engagement
    • 29. Goals and Characteristics of a SOA <ul><li>Improved Adaptability and Agility </li></ul><ul><ul><li>Respond to business needs in near real-time </li></ul></ul><ul><li>Functional Reusability </li></ul><ul><ul><li>Eliminate the need for large scale rip and replace </li></ul></ul><ul><li>Independent Change Management </li></ul><ul><ul><li>Focus on configuration rather than programming </li></ul></ul><ul><li>Interoperability instead of point-to-point integration </li></ul><ul><ul><li>Loosely-coupled framework, services in network </li></ul></ul><ul><li>Orchestrate rather than integrate </li></ul><ul><ul><li>Configuration rather than development to deliver business needs </li></ul></ul>
    • 30. Business Benefits of Loosely Coupled Approach
    • 31. Thanks!

    ×