服务计算技术丛书：SOA设计模式（英文版）

图书标准信息

• 作者 [美]Thomas Erl 著
• 出版社 科学出版社
• 出版时间 2012-03
• 版次 1
• ISBN 9787030336392
• 定价 125.00元
• 装帧 平装
• 开本 16开
• 纸张 其他
• 页数 818页
• 正文语种 英语
• 丛书 服务计算技术丛书

【内容简介】

《服务计算技术丛书：SOA设计模式（英文版）》首先介绍了面向服务架构（SOA）的85种设计模式，包括业务清单的设计、实现和治理模式，与设计领域有关的业务级架构模式，业务组合模式，以及混合模式等；然后在最后一章讨论了源于服务计算的架构作用。书中配有大量的设计实例、关于重点内容的小提示，以及400多幅插图。全书章节之间以模式目录的形式提供了SOA设计模式、服务计算的战略目标、不同SOA类型和业务设计范例之间的清晰链接。
《服务计算技术丛书：SOA设计模式（英文版）》可供SOA领域的软件架构师、高级软件工程师、分析师、应用科研人员等参考学习。

【目录】

Foreword
Chapter1:Introduction
1.1ObjectivesofthisBook
1.2WhothisBookisFor
1.3WhatthisBookDoesNotCover
TopicsCoveredbyOtherBooks
WebServiceandRESTServiceDesignPatterns
SOAStandardizationEfforts
1.4RecommendedReading
1.5HowthisBookisOrganized
PartI:Fundamentals
PartII:ServiceInventoryDesignPatterns
PartIII:ServiceDesignPatterns
PartIV:ServiceCompositionDesignPatterns
PartV:Supplemental
PartVI:Appendices
1.6Symbols,Figures,StyleConventions
SymbolLegend
HowColorisUsed
DataFlowandDirectionalityConventions
PatternDocumentationConventions
1.7AdditionalInformation
Updates,Errata,andResources(www.soabooks.com)
VisioStencil(www.soabooks.com)
CommunityPatternsSite(www.soapatterns.org)
MasterGlossary(www.soaglossary.com)
SupplementaryPosters(www.soaposters.com)
TheSOAMagazine(www.soamag.com)
ReferencedSpecifications(www.soaspecs.com)
NotificationService
ContacttheAuthor
Chapter2:CaseStudyBackground
2.1Case#1Background:CutitSawsLtd.
History
TechnicalInfrastructureandAutomationEnvironment
BusinessGoalsandObstacles
2.2Case#2Background:AlleywoodLumberCompany
History
TechnicalInfrastructureandAutomationEnvironment
BusinessGoalsandObstacles
2.3Case#3Background:ForestryRegulatoryCommission(FRC)
History
TechnicalInfrastructureandAutomationEnvironment
BusinessGoalsandObstacles
PARTI:Fundamentals
CHAPTER3:BasicTermsandConcepts
PurposeofthisIntroductoryChapter
3.1ArchitectureFundamentals
AClassicAnalogyforArchitectureandInfrastructure
TechnologyArchitecture
TechnologyInfrastructure
SoftwareProgram
RelationshiptoDesignFramework
3.2Service-OrientedComputingFundamentals
Service-OrientedComputing
Service-Orientation
Service-OrientedArchitecture(SOA)
Service
ServiceCapability
ServiceConsumer
ServiceComposition
ServiceInventory
Service-OrientedAnalysis
ServiceCandidate
3.3ServiceImplementationMediums
ServicesasComponents
ServicesasWebServices
RESTServices
CHAPTER4:TheArchitectureofService-Orientation
PurposeofthisIntroductoryChapter
4.1TheMethodofService-Orientation
PrinciplesofService-Orientation
StrategicGoalsofService-OrientedComputing
4.2TheFourCharacteristicsofSOA
Business-Driven
Vendor-Neutral
Enterprise-Centric
Composition-Centric
4.3TheFourCommonTypesofSOA
ServiceArchitecture
InformationHiding
DesignStandards
ServiceContracts
ServiceAgents
ServiceCapabilities
ServiceCompositionArchitecture
NestedCompositions
TaskServicesandAlternativeCompositions
CompositionsandInfrastructure
ServiceInventoryArchitecture
Service-OrientedEnterpriseArchitecture
ArchitectureTypesandScope
ArchitectureTypesandInheritance
OtherFormsofService-OrientedArchitecture
Inter-BusinessServiceArchitecture
Service-OrientedCommunityArchitecture
4.4TheEndResultofService-Orientation
CHAPTER5:UnderstandingSOADesignPatterns
PurposeofthisIntroductoryChapter
5.1FundamentalTerminology
What'saDesignPattern?
What'saCompoundPattern?
What'saDesignPatternLanguage?
What'saDesignPatternCatalog?
5.2HistoricalInfluences
Alexander'sPatternLanguage
Object-OrientedPatterns
SoftwareArchitecturePatterns
EnterpriseApplicationArchitecturePatterns
EAIPatterns
SOAPatterns
5.3PatternNotation
PatternSymbols
PatternFigures
PatternApplicationSequenceFigures
PatternRelationshipFigures
CompoundPatternHierarchyFigures
Capitalization
PageNumberReferences
5.4PatternProfiles
Summary
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
5.5PatternswithCommonCharacteristics
CanonicalPatterns
CentralizationPatterns
5.6KeyDesignConsiderations
?Enterprise?vs.?Enterprise-wide?
DesignPatternsandDesignPrinciples
DesignPatternsandDesignGranularity
PARTII:SERVICEINVENTORYDESIGNPATTERNS
CHAPTER6:FoundationalInventoryPatterns
HowInventoryDesignPatternsRelatetoSOADesignCharacteristics
HowFoundationalInventoryandServicePatternsRelate
HowCaseStudiesareUsedinthisChapter
6.1InventoryBoundaryPatterns
EnterpriseInventory
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
DomainInventory
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
6.2InventoryStructurePatterns
ServiceNormalization
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
LogicCentralization
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
ServiceLayers
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
6.3InventoryStandardizationPatterns
CanonicalProtocol
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
CanonicalSchema
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
CHAPTER7:LogicalInventoryLayerPatterns
CombiningLayers
BusinessLogicandUtilityLogic
AgnosticLogicandNon-AgnosticLogic
ServiceLayersandLogicTypes
UtilityAbstraction
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
EntityAbstraction
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
ProcessAbstraction
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
CHAPTER8:InventoryCentralizationPatterns
ProcessCentralization
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
SchemaCentralization
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
PolicyCentralization
Problems
Solution
Application
Impacts
Relationships
CaseStudyExample
RulesCentralization
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
CHAPTER9:InventoryImplementationPatterns
DualProtocols
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
CanonicalResources
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
StateRepository
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
StatefulServices
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
ServiceGrid
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
InventoryEndpoint
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
Cross-DomainUtilityLayer
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
CHAPTER10:InventoryGovernancePatterns
CanonicalExpression
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
MetadataCentralization
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
CanonicalVersioning
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
PARTIII:SERVICEDESIGNPATTERNS
CHAPTER11:FoundationalServicePatterns
CaseStudyBackground
11.1ServiceIdentificationPatterns
FunctionalDecomposition
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
ServiceEncapsulation
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
11.2ServiceDefinitionPatterns
AgnosticContext
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
Non-AgnosticContext
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
AgnosticCapability
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
CHAPTER12:ServiceImplementationPatterns
ServiceFacade
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
RedundantImplementation
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
ServiceDataReplication
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
PartialStateDeferral
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
PartialValidation
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
UIMediator
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
CHAPTER13:ServiceSecurityPatterns
CaseStudybackground
ExceptionShielding
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
MessageScreening
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
TrustedSubsystem
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
ServicePerimeterGuard
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
CHAPTER14:ServiceContractDesignPatterns
DecoupledContract
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
ContractCentralization
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
ContractDenormalization
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
ConcurrentContracts
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
ValidationAbstraction
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
CHAPTER15:LegacyEncapsulationPatterns
LegacyWrapper
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
Multi-ChannelEndpoint
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
FileGateway
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
CHAPTER16:ServiceGovernancePatterns
CompatibleChange
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
VersionIdentification
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
TerminationNotification
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
ServiceRefactoring
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
ServiceDecomposition
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
ProxyCapability
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
DecomposedCapability
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
DistributedCapability
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
PARTIV:SERVICECOMPOSITIONDESIGNPATTERNS
CHAPTER17:CapabilityCompositionPatterns
CapabilityComposition
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
CapabilityRecomposition
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
CHAPTER18:ServiceMessagingPatterns
ServiceMessaging
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
MessagingMetadata
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
ServiceAgent
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
IntermediateRouting
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
StateMessaging
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
ServiceCallback
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
ServiceInstanceRouting
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
AsynchronousQueuing
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
ReliableMessaging
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
Event-DrivenMessaging
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
CHAPTER19:CompositionImplementationPatterns
AgnosticSub-Controller
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
CompositionAutonomy
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
AtomicServiceTransaction
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
CompensatingServiceTransaction
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
CHAPTER20:ServiceInteractionSecurityPatterns
DataConfidentiality
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
DataOriginAuthentication
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
DirectAuthentication
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
BrokeredAuthentication
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
CHAPTER21:TransformationPatterns
DataModelTransformation
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
DataFormatTransformation
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
ProtocolBridging
Problem
Solution
Application
Impacts
Relationships
CaseStudyExample
PARTV:SUPPLEMENTAL
CHAPTER22:CommonCompoundDesignPatterns
"Compound"vs."Composite"
CompoundPatternsandPatternRelationships
JointApplicationvs.CoexistentApplication
CompoundPatternsandPatternGranularity
Orchestration
EnterpriseServiceBus
ServiceBroker
CanonicalSchemaBus
OfficialEndpoint
FederatedEndpointLayer
Three-LayerInventory
CHAPTER23:StrategicArchitectureConsiderations
IncreasedFederation
IncreasedIntrinsicInteroperability
IncreasedVendorDiversificationOptions
IncreasedBusinessandTechnologyAlignment
IncreasedROI
IncreasedOrganizationalAgility
ReducedITBurden
CHAPTER24:PrinciplesandPatternsattheU.S.DepartmentofDefense
TheBusinessOperatingEnvironment(BOE)
Principles,Patterns,andtheBOE
IncorporationofInformationAssurance(IA)
AdherencetoStandards
DataVisibility,Accessibility,andUnderstandabilitytoSupportDecisionMakers
LooselyCoupledServices
AuthoritativeSourcesofTrustedData
Metadata-DrivenFrameworkforSeparationfromTechnicalDetails
SupportUseofOpenSourceSoftware
EmphasizeUseofService-EnabledCommercialOff-the-Shelf(COTS)Software
ParticipationintheDoDEnterprise
SupportMobility-Users&Devices
TheFutureofSOAandtheDoD
SOADoD.org
PARTVI:APPENDICES
APPENDIXA:CaseStudyConclusion
CutitSawsLtd
AlleywoodLumberCompany
ForestryRegulatoryCommission(FRC)
APPENDIXB:CandidatePatterns
APPENDIXC:PrinciplesofService-Orientation
StandardizedServiceContract
ServiceLooseCoupling
ServiceAbstraction
ServiceReusability
ServiceAutonomy
ServiceStatelessness
ServiceDiscoverability
ServiceComposability
APPENDIXD:PatternsandPrinciplesCross-Reference
APPENDIXE:PatternsandArchitectureTypesCross-Reference
AbouttheAuthor
AbouttheContributors
IndexofPatterns
Index