Recommendation and Translation Plan of service oreiented architecture in the real world

Recommendation and Translation Plan of service oreiented architecture in the real world

 

What is SOA? Why do we need SOA? What is a service? How do we design services? How does SOA provide solutions for businesses? All of these, just like the story of the blind man and the elephant in this book, are the answers of everyone. This book tries to penetrate all these fog and unveil the mysteries of SOA, SOA is also a clear truth.

Unlike ordinary books, this book is full of paper, empty and cloud. As the author's language goes through the cloud, we can also feel the excitement and passion in our words. With my own English skills, I still feel that reading this book is a great pleasure. When you read the original books with excellent English skills, you will certainly feel more.

Although the English level is not very good, but out of this book's love, it is planned to translate this book, as an opportunity to study this book in depth, second, to learn more about SoA through this book, we can try to understand the pain of reading English. Translation of this book is purely personal pleasure and does not aim at profit. It is inappropriate for readers, Hai Han.

Due to heavy workload, the translation speed is not necessarily very fast. We plan to translate one chapter every two weeks. The first part of this article is pure directory introduction. From the directory, we can know the component of the content. It is indeed a good book worth looking forward to and having!

 

 

 

Directory

Chapter 1: Service-Oriented Architecture (SOA)

Reader benefits

Thank you

Introduction to SOA

SOA elephant

Simple SOA Definition

Absurd and true SOA

Evolution of SOA

Why must I focus on SOA?

Understanding services

Service Design Principles

Principle 1: Clear borders

Principle 2: Service autonomy

Principle 3: service sharing solutions and protocols, not class

Principle 4: Policy-based service compatibility

SOA abstract Reference Model

Exposure

Combination

Consumption

Rebuild architecture capability

Messages and services

Workflow and process

Data

User Experience

Identity and access

Management

Public Architecture capability

Public Architecture capability and abstract SOA Model

Exposure

Combination

Consumption

Summary

Reference

Chapter 2: messages and services

Reader benefits

Thank you

Understanding services

SOA Maturity Model (another ??)

Service Classification

Service Lifecycle

Analysis Service

Development Service

Test Service

Provide services

Operation Service

Consumption Service

Service Change Management

Service exited

Service scenarios

Information Integration

Legacy System Integration

Process Management

Consistent access

Resource virtualization

Process externalization

Other scenarios

SOA and end users

What is a combined application?Program?

What is a combined application like?

How can a combined application be successful based on the expected benefits?

Conclusion

SOA Case Study: Australian Federal Bank

References

Chapter 3: workflows and processes

Reader benefits

Thank you

Understanding workflows

What is a workflow?

Workflow terminology

Why Workflow

Workflow Model

Workflow Protocol

Collaborative Problem Solving

Script-based operations

Rules and policies

Value of the workflow platform

More colloquial Publicity

Platform features

When a general workflow is running

Direct hit

Workflow Declaration

Agility

Abstraction

Workflows are everywhere.

Workflow is clear

Workflow is flow

Workflows are all-encompassing.

The workflow is transparent.

Understand the connection between BizTalk Server and WF

Conclusion

Case study: $ saved car Organization

References

Chapter 4: Data

Reader benefits

Thank you

Data Challenges Faced by SOA

Overview

Data integration challenges

Database measurability

Master Data Management (MDM)

What is primary data?

Customer Data Integration (CDI)

Product Information Management (PIM)

Master Data Management (MDM) Hub Architecture

Central architecture type

Architecture challenges

Version and level

Breeding and Synchronization

Release update

Data consistency and reliability

Metadata

Management and Control

Data Processing

Output

Report

Workflow and business rules

Tools

Conclusion

SOA Case Study: London stock market

References

Chapter 5: User Interaction

Reader benefits

Thank you

What is architecture?

Introduce a framework on UX

Interface

Interaction

Infrastructure

Case study: Zurich Airlines

References

Chapter 6: identity and access

Reader benefits

Thank you

Identity and access

Overview

Trusted subsystem Design

Current practice

Trusted subsystem Design

Trusted subsystem process scaling

Trusted subsystem Policy

A smooth original caller ID statement

Identity/evidence ing

Benefits of this design

One identity meta System

What is an identity metadata system?

Functions of identity in context

Identity law

Roles in the identity meta System

Components in the identity meta System

One identity meta system architecture: WS-* Web Services

Conclusion

Case study: outu

References