SOA Made Simple

SOA Made Simple

by Lonneke Dikmans, Ronald van Luttikhuizen
Released December 2012
Publisher(s): Packt Publishing
ISBN: 9781849684163

Read it now on the O’Reilly learning platform with a 10-day free trial.

O’Reilly members get unlimited access to books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.

Start your free trial

Book description

Discover the true meaning behind the buzzword that is ‘Service Oriented Architecture’

  • Get to grips with clear definitions of ‘Service’ and ‘Architecture’ to understand the full SOA picture
  • Read about SOA in simple terms from Oracle ACE Directors for SOA and Middleware in this book and e-book
  • A concise, no-nonsense guide to demystifying Service Oriented Architecture

In Detail

SOA is an industry term which is often preached like a religion rather than taught like a technology, and over time, grasping the concept has become unnecessarily difficult. Many companies proclaim that they don’t know where to begin with SOA, while others have begun their SOA effort but haven’t reaped the benefits they were convinced it would bring. “SOA Made Simple” unveils the true meaning of Service Oriented Architecture and how to make it successful so that you can confidently explain SOA to anyone!

“SOA Made Simple” explains exactly what SOA is in simple terminology and by using real-life examples. Once a simple definition is clear in your mind, you’ll be guided through what SOA solves, when and why you should use it, and how to set up, design and categorize your SOA landscape. With this book in hand you’ll learn to keep your SOA strategy successful as you expand on it.

“SOA Made Simple” demystifies SOA, simply. It is not difficult to grasp, but for various reasons SOA is often made unnecessarily complex. Service-orientation is already a very natural way of thinking for business stakeholders that want to realize and sell services to potential clients, and this book helps you to realize that concept both in theory and practice.

You’ll begin with a clear and simple explanation of what SOA is and why we need it. You’ll then be presented with plain facts about the key ingredients of a service, and along the way learn about service design, layering and categorizing, some major SOA platform offerings as well as governance and successful implementation.

After reading “SOA Made Simple” you will have a clear understanding of what SOA is so you can implement and govern SOA in your own organization.

Table of contents

  1. SOA Made Simple
    1. Table of Contents
    2. SOA Made Simple
    3. Credits
    4. About the Authors
    5. About the Reviewers
    6. www.PacktPub.com
      1. Support files, eBooks, discount offers and more
      2. Why Subscribe?
      3. Free Access for Packt account holders
      4. Instant Updates on New Packt Books
    7. Preface
      1. What this book covers
      2. What you need for this book
      3. Who this book is for
      4. Conventions
      5. Reader feedback
      6. Customer support
        1. Downloading the example code
        2. Errata
        3. Piracy
        4. Questions
    8. 1. Understanding the Problem
      1. The importance of information
        1. Example – insurance company
        2. Mismatch between business and IT
        3. Duplication of functionality and data
        4. Example – insurance company
        5. Process silos
          1. Example – utility companies
          2. Example – international software company
          3. Example – insurance company
        6. Strategies to stay ahead
          1. Example – a software company
      2. Architecture as a tool
        1. Layering of architecture
        2. Models
          1. Requirements
        3. Architecture ontology
          1. Enterprise architecture
          2. Reference architecture
          3. Solution architecture
          4. Project architecture
          5. Software architecture
          6. Service Oriented Architecture
      3. Summary
    9. 2. The Solution
      1. What is a service?
        1. Elements of a service – contract, interface, and implementation
          1. Example – let's have breakfast
            1. Contract
            2. Interface
            3. Implementation
          2. Example – ordering a passport
          3. Consumer and provider
            1. Dealing with lots of service providers – service registry
            2. How can you make sure that people use a service?
        2. From sunny-side-up eggs to IT
          1. Example – international software company revisited
            1. Contract
            2. Interface
            3. Implementation
          2. Consumer and provider
            1. Reuse
      2. Drivers for services
        1. Common myths
          1. Every service has to be automated by software
          2. Every service is a web service
          3. Consumers of services are always IT systems
      3. Putting it together – what is SOA?
      4. Solutions
        1. Example – utility company
        2. International software company – changing existing processes
        3. Functional duplication – rationalizing application landscapes
        4. Standardization – enabling change
      5. Summary
    10. 3. Service Identification and Design
      1. Service identification
        1. Top-down
          1. Example of top-down service identification
            1. Business service identification
            2. Information service identification
            3. Technical service identification
        2. Bottom-up
        3. Meet in the middle
        4. I have identified my services, now what?
      2. Service design
        1. Provide value
        2. Meaningful
        3. Implementation hiding
        4. Trust
        5. Idempotent
        6. Isolated
        7. Interoperable
        8. Isolation
          1. Example: print service
        9. Trust
          1. Security
          2. Fault-prevention and handling
            1. Business faults
            2. Faulty user input
            3. Technical and software faults
        10. Idempotency
          1. Idempotency and statefulness
        11. Granularity
          1. How big should my lasagna be?
          2. Classification
        12. Reusability
          1. Example – reusability
      3. Example – good or bad service?
      4. Service definition revisited
      5. Summary
    11. 4. Classification of Services
      1. Service classification revisited
        1. Example – insurance company
        2. Other classifications
          1. Actor type
          2. Channel
          3. Organizational boundaries
          4. Security level
          5. Architectural layer
        3. Combining classifications
        4. Why classify your services?
      2. Composability
        1. Aggregation versus orchestration
          1. Example – DocumentService as a composite service
      3. Elementary services
        1. Realization
      4. Composite services
        1. Where to put the composition logic?
        2. Implementation
          1. Example 1 – database link
          2. Example 2 – service invocation
      5. Process services
        1. Implementation
      6. Isolation and composition – a contradiction?
      7. Passing information from smaller to larger services
      8. Summary
    12. 5. The SOA Platform
      1. Overview
      2. Services
        1. Implementation
          1. Using existing software
          2. Build the implementation
        2. Interfaces
          1. Proprietary interfaces
          2. Web services
            1. SOAP-based services
            2. RESTful services
        3. Contracts and Policies
      3. Events
        1. Interfaces for events
      4. Service composition
        1. Enterprise Service Bus
        2. Business Process Management
        3. Case Management
      5. Business rules
      6. User interface
        1. Integrated user interfaces
        2. Information mismatch
      7. Security
        1. Applying security in your SOA
      8. Service registry and service repository
        1. Canonical Data Model
      9. Design tooling
      10. Development tooling
      11. Example – Order-to-cash revisited
        1. Designing the solution
        2. Developing the solution
        3. Running the solution
      12. Summary
    13. 6. Solution Architectures
      1. Comprehensive suite or best of breed
      2. Comparison
      3. Oracle
        1. Services
        2. Events
          1. Oracle Event Processing (OEP)
          2. Business Activity Monitoring (BAM)
        3. Service composition
          1. Oracle Service Bus
          2. Oracle SOA Suite
          3. Oracle BPM Suite
        4. Business rules
        5. User interface
        6. Security
        7. Registry and repository
        8. Design tooling
          1. Design tooling for developers
          2. Design tooling for business analysts
        9. Development tooling
        10. Test tooling
          1. Testing transformations
          2. SCA testing framework
          3. Testing from the console
        11. Deployment tooling
          1. Deployment from the IDE
          2. Deployment from the console
          3. Deployment using scripting
        12. Monitoring
        13. Error handling
      4. IBM
        1. Services
        2. Events
          1. WebSphere Operational Decision Management
          2. IBM Business Monitor
        3. Service composition
          1. IBM WebSphere Enterprise Service Bus
          2. IBM Business Process Manager
        4. Business rules
        5. User interface
        6. Security
        7. Registry and repository
        8. Design tooling
          1. Services
          2. Composite services
        9. Development tooling
        10. Test tooling
        11. Deployment tooling
          1. Deployment from the IDE
          2. Deployment from the web interface of the server
          3. Deployment scripts
        12. Monitoring
        13. Error handling
      5. Microsoft
        1. Services
        2. Events
          1. Message-oriented middleware
          2. Complex Event Processing (CEP)
          3. Business Activity Monitoring
        3. Service composition
          1. BizTalk Server
          2. Windows Server AppFabric
        4. Business rules
        5. User interface
        6. Security
        7. Registry and repository
        8. Design tooling
        9. Development tooling
        10. Test tooling
        11. Deployment tooling
          1. BizTalk Server
        12. Monitoring
        13. Error handling
      6. Summary
    14. 7. Creating a Roadmap, How to Spend Your Money and When?
      1. Organize the SOA effort
      2. Business case – benefits for different stakeholders
        1. Business case explained
        2. Company as a whole
          1. Example 1 – insurance company WATB needs shorter time to market
            1. Summary of scenarios
            2. Analysis of the scenarios
          2. Example 2 – insurance company TPIR needs to decrease operational cost
            1. Summary of scenarios
            2. Analysis of the scenarios
        3. IT
          1. Example – insurance company TMS needs to consolidate systems
        4. Departmental benefits
          1. Example – insurance company X wants to cut cost
          2. Analysis of the scenarios
      3. Approaches
          1. Example – Document Management Service
          2. Top-down identification
          3. Bottom-up identification
          4. Meet in the middle
      4. Roadmap
        1. Work packages
          1. Service by service
          2. Process by process
          3. Feature by feature
          4. System by system
          5. Comparison
      5. Maturity and stages
        1. Stage 0: Starting with SOA
        2. Stage 1: Newlyweds
        3. Stage 2: Live
        4. Stage 3: Growing up
        5. Stage 4: Experience
        6. Stage 5: Maintenance
      6. Summary
    15. 8. Life Cycle Management
      1. Service stages
      2. Versioning of services
        1. Type of change – contract, interface, and implementation
          1. Changing the contract
          2. Changing the interface
          3. Changing the implementation
        2. Versioning schemes
          1. Versioning and life cycle stages
          2. Making the version explicit for service consumers
        3. Communicating change
      3. Tooling
        1. Standards
        2. Information needed
          1. Find services
          2. Troubleshooting
          3. Change process
        3. Registries and repositories in your IT landscape
          1. Enterprise architecture tools
          2. Business Process Management tool
          3. Configuration Management Database
          4. Bug and issue tracker system
          5. ESB
          6. Business Activity Monitoring
          7. Infrastructure monitoring
      4. Summary
    16. 9. Pick your Battles
      1. Governance
      2. Architecture process
        1. Ad hoc business need
          1. Define the solution
          2. Deviations
          3. Integration in the solution architecture
        2. Planned feature
        3. Pick your battles
      3. Development process
        1. Pick your battles
      4. Operations
        1. Pick your battles
      5. Change management
        1. Pick your battles
      6. Summary
    17. 10. Methodologies and SOA
      1. Demand management
        1. Methodology
        2. Impact of SOA
      2. Project management
        1. Methodology
        2. Impact of SOA
      3. Software development
        1. Methodology
        2. Impact of SOA
      4. Application management
        1. Methodology
        2. Impact of SOA
      5. IT service and operations management
        1. Methodology
        2. Impact of SOA
      6. Summary
    18. Index

Product information

  • Title: SOA Made Simple
  • Author(s): Lonneke Dikmans, Ronald van Luttikhuizen
  • Release date: December 2012
  • Publisher(s): Packt Publishing
  • ISBN: 9781849684163