SOA Made Simple
eBook:
$26.99
Formats:
Formats:
$22.94
save 15%!
save 15%!
Print + free eBook + free PacktLib access to the book:
$71.98
Print cover: $44.99
$44.99
save 37%!
save 37%!
Free Shipping!
UK, US, Europe and selected countries in Asia.
| Also available on: |
|
- 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
Book Details
Language : EnglishPaperback : 292 pages [ 235mm x 191mm ]
Release Date : December 2012
ISBN : 1849684162
ISBN 13 : 9781849684163
Author(s) : Lonneke Dikmans , Ronald van Luttikhuizen
Topics and Technologies : All Books, Enterprise, SOA
Table of Contents
PrefaceChapter 1: Understanding the Problem
Chapter 2: The Solution
Chapter 3: Service Identification and Design
Chapter 4: Classification of Services
Chapter 5: The SOA Platform
Chapter 6: Solution Architectures
Chapter 7: Creating a Roadmap, How to Spend Your Money and When?
Chapter 8: Life Cycle Management
Chapter 9: Pick your Battles
Chapter 10: Methodologies and SOA
Index
- Chapter 1: Understanding the Problem
- The importance of information
- Example – insurance company
- Mismatch between business and IT
- Duplication of functionality and data
- Example – insurance company
- Process silos
- Example – utility companies
- Example – international software company
- Example – insurance company
- Strategies to stay ahead
- Example – a software company
- Architecture as a tool
- Layering of architecture
- Models
- Requirements
- Architecture ontology
- Enterprise architecture
- Reference architecture
- Solution architecture
- Project architecture
- Software architecture
- Service Oriented Architecture
- Summary
- Chapter 2: The Solution
- What is a service?
- Elements of a service – contract, interface, and implementation
- Example – let's have breakfast
- Example – ordering a passport
- Consumer and provider
- From sunny-side-up eggs to IT
- Example – international software company revisited
- Consumer and provider
- Drivers for services
- Common myths
- Every service has to be automated by software
- Every service is a web service
- Consumers of services are always IT systems
- Putting it together – what is SOA?
- Solutions
- Example – utility company
- International software company – changing existing processes
- Functional duplication – rationalizing application landscapes
- Standardization – enabling change
- Summary
- Chapter 3: Service Identification and Design
- Service identification
- Top-down
- Example of top-down service identification
- Bottom-up
- Meet in the middle
- I have identified my services, now what?
- Service design
- Provide value
- Meaningful
- Implementation hiding
- Trust
- Idempotent
- Isolated
- Interoperable
- Isolation
- Example: print service
- Trust
- Security
- Fault-prevention and handling
- Idempotency
- Idempotency and statefulness
- Granularity
- How big should my lasagna be?
- Classification
- Reusability
- Example – reusability
- Example – good or bad service?
- Service definition revisited
- Summary
- Chapter 4: Classification of Services
- Service classification revisited
- Example – insurance company
- Other classifications
- Actor type
- Channel
- Organizational boundaries
- Security level
- Architectural layer
- Combining classifications
- Why classify your services?
- Composability
- Aggregation versus orchestration
- Example – DocumentService as a composite service
- Elementary services
- Realization
- Composite services
- Where to put the composition logic?
- Implementation
- Example 1 – database link
- Example 2 – service invocation
- Process services
- Implementation
- Isolation and composition – a contradiction?
- Passing information from smaller to larger services
- Summary
- Chapter 5: The SOA Platform
- Overview
- Services
- Implementation
- Using existing software
- Build the implementation
- Interfaces
- Proprietary interfaces
- Web services
- Contracts and Policies
- Events
- Interfaces for events
- Service composition
- Enterprise Service Bus
- Business Process Management
- Case Management
- Business rules
- User interface
- Integrated user interfaces
- Information mismatch
- Security
- Applying security in your SOA
- Service registry and service repository
- Canonical Data Model
- Design tooling
- Development tooling
- Example – Order-to-cash revisited
- Designing the solution
- Developing the solution
- Running the solution
- Summary
- Chapter 6: Solution Architectures
- Comprehensive suite or best of breed
- Comparison
- Oracle
- Services
- Events
- Oracle Event Processing (OEP)
- Business Activity Monitoring (BAM)
- Service composition
- Oracle Service Bus
- Oracle SOA Suite
- Oracle BPM Suite
- Business rules
- User interface
- Security
- Registry and repository
- Design tooling
- Design tooling for developers
- Design tooling for business analysts
- Development tooling
- Test tooling
- Testing transformations
- SCA testing framework
- Testing from the console
- Deployment tooling
- Deployment from the IDE
- Deployment from the console
- Deployment using scripting
- Monitoring
- Error handling
- IBM
- Services
- Events
- WebSphere Operational Decision Management
- IBM Business Monitor
- Service composition
- IBM WebSphere Enterprise Service Bus
- IBM Business Process Manager
- Business rules
- User interface
- Security
- Registry and repository
- Design tooling
- Services
- Composite services
- Development tooling
- Test tooling
- Deployment tooling
- Deployment from the IDE
- Deployment from the web interface of the server
- Deployment scripts
- Monitoring
- Error handling
- Microsoft
- Services
- Events
- Message-oriented middleware
- Complex Event Processing (CEP)
- Business Activity Monitoring
- Service composition
- BizTalk Server
- Windows Server AppFabric
- Business rules
- User interface
- Security
- Registry and repository
- Design tooling
- Development tooling
- Test tooling
- Deployment tooling
- BizTalk Server
- Monitoring
- Error handling
- Summary
- Chapter 7: Creating a Roadmap, How to Spend Your Money and When?
- Organize the SOA effort
- Business case – benefits for different stakeholders
- Business case explained
- Company as a whole
- Example 1 – insurance company WATB needs shorter time to market
- Example 2 – insurance company TPIR needs to decrease operational cost
- IT
- Example – insurance company TMS needs to consolidate systems
- Departmental benefits
- Example – insurance company X wants to cut cost
- Analysis of the scenarios
- Approaches
- Example – Document Management Service
- Top-down identification
- Bottom-up identification
- Meet in the middle
- Roadmap
- Work packages
- Service by service
- Process by process
- Feature by feature
- System by system
- Comparison
- Maturity and stages
- Stage 0: Starting with SOA
- Stage 1: Newlyweds
- Stage 2: Live
- Stage 3: Growing up
- Stage 4: Experience
- Stage 5: Maintenance
- Summary
- Chapter 8: Life Cycle Management
- Service stages
- Versioning of services
- Type of change – contract, interface, and implementation
- Changing the contract
- Changing the interface
- Changing the implementation
- Versioning schemes
- Versioning and life cycle stages
- Making the version explicit for service consumers
- Communicating change
- Tooling
- Standards
- Information needed
- Find services
- Troubleshooting
- Change process
- Registries and repositories in your IT landscape
- Enterprise architecture tools
- Business Process Management tool
- Configuration Management Database
- Bug and issue tracker system
- ESB
- Business Activity Monitoring
- Infrastructure monitoring
- Summary
- Chapter 9: Pick your Battles
- Governance
- Architecture process
- Ad hoc business need
- Define the solution
- Deviations
- Integration in the solution architecture
- Planned feature
- Pick your battles
- Development process
- Pick your battles
- Operations
- Pick your battles
- Change management
- Pick your battles
- Summary
- Chapter 10: Methodologies and SOA
- Demand management
- Methodology
- Impact of SOA
- Project management
- Methodology
- Impact of SOA
- Software development
- Methodology
- Impact of SOA
- Application management
- Methodology
- Impact of SOA
- IT service and operations management
- Methodology
- Impact of SOA
- Summary
Lonneke Dikmans
Ronald van Luttikhuizen
Code Downloads
Download the code and support files for this book.
Submit Errata
Please let us know if you have found any errors not listed on this list by completing our errata submission form. Our editors will check them and add them to this list. Thank you.
Sample chapters
You can view our sample chapters and prefaces of this title on PacktLib or download sample chapters in PDF format.
Frequently bought together
+
=
50% Off
the eBooks
the eBooks
Buy both these recommended eBooks together and get 50% off the total price
- Start logically by understanding the misalignment of IT and Business and the problems it causes
- Gradually learn about the solution to this misalignment with SOA concepts such as service, solution architecture, and more
- Put together clear definitions of ‘Service’ and ‘Architecture’ to understand the full SOA picture
- Fully understand how to distinguish between both well and badly designed services and pinpoint the reasons for each
- Get to grips with the different service layers, guidelines and principles of service design
- Learn about the building blocks of SOA, like BPM and Enterprise Service Bus
- Dive into the realization and maintenance of your SOA once the concept is clear
- Think about SOA in historic perspective: the evolution from EAI, CBD, OO and so on
- Understand how to pick your battles once you finally get started with SOA to make it a successful effort in your own organization!
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.
“SOA Made Simple” is a concise and indispensable handbook for finally understanding exactly what Service Oriented Architecture is. Split into three clear sections, in this book you’ll learn from both theory as well as step-by-step implementation examples to aid in your understanding of this often poorly- articulated industry term.
If you are an architect who wants to be completely clear in your understanding of what SOA is, then this book is essential. In fact, anyone (designer, developer, administrator or team lead) who is implementing or about to implement an architecture in an IT environment should not miss out on “SOA Made Simple”.
Some previous experience with general software architecture is required, but this guide will tell you everything you need to know about SOA in a clear and easy fashion.
