架构英文

系统架构：复杂系统的产品设计与开发-英文版（文字非扫描）

,,,,47References48thinkingaboutcomplexSystems493.1introduction493.2complexityinSystems493.3DecompositionofSystems533.4SpecialLogicalrelationships573.5reasoningthroughcomplexSystems583.6Architecturerepresentationtools:SysmLandOPm593.7Summary62References64analysisofSystemarchitecture654CoNTeNTSPart3CreatingSystemarchitecture191chapter54.7Summary96References96Function975.1introduction975.2FunctioninArchitecture975.3AnalysisofexternalFunctionandValue1035.4AnalysisofinternalFunction1085.5AnalysisofFunctionalinteractionsandFunctionalArchitecture1125.6SecondaryValue-relatedexternalandinternalFunctions1225.7Summary123References123SystemArchitecture1246.1introduction1246.2SystemArchitecture:FormandFunction1256.3Non-idealities,SupportingLayers,andinterfacesinSystemArchitecture1356.4OperationalBehavior1396.5reasoningaboutArchitectureusingrepresentations1436.6Summary150References150Solution-NeutralFunctionandconcepts1517.1introduction1517.2identifyingtheSolution-NeutralFunction1547.3concept1567.4integratedconcepts1667.5conceptsofOperationsandServices1717.6Summary172References173FromconcepttoArchitecture1748.1introduction1748.2DevelopingtheLevel1Architecture1768.3DevelopingtheLevel2Architecture1808.4homeDataNetworkArchitectureatLevel21848.5modularizingtheSystematLevel11878.6Summary189References190chapter6chapter7chapter8chapter9theroleoftheArchitect1929.1introduction192chapter109.2AmbiguityandtheroleoftheArchitect1929.3theProductDevelopmentProcess1989.4Summary206References210upstreamandDownstreaminfluencesonSystemArchitect架构英文ure21110.1introduction21110.2upstreaminfluence:corporateStrategy21210.3upstreaminfluence:marketing21510.4upstreaminfluence:regulationandPseudo-regulatoryinfluences21810.5upstreaminfluence:technologyinfusion22010.6Downstreaminfluence:implementationcoding,manufacturing,andSupplychainmanagement22110.7Downstreaminfluence:Operations22410.8Downstreaminfluence:DesignforX22610.9Downstreaminfluence:ProductandSystemevolution,andProductFamilies22810.10theProductcase:ArchitectureBusinesscaseDecision(ABcD)23110.11Summary235References238translatingNeedsintoGoals24011.1introduction24011.2identifyingBeneficiariesandStakeholders24111.3characterizingNeeds25011.4interpretingNeedsasGoals25811.5PrioritizingGoals26411.6Summary267References273ApplyingcreativitytoGeneratingaconcept27612.1introduction27612.2Applyingcreativitytoconcept27712.3Developtheconcepts28212.4expandtheconceptsandDeveloptheconceptFragments28312.5evolveandrefinetheintegratedconcepts28812.6SelectaFewintegratedconceptsforFurtherDevelopment29112.7Summary293References298Decompositionasatoolformanagingcomplexity30013.1introduction300chapter11chapter12chapter13CoNTeNTS56CoNTeNTS13.2understandingcomplexity30013.3managingcomplexity30913.4Summary317References322Part4architectureasDecisions323chapter14SystemArchitectureasaDecision-makingProcess32514.1introduction32514.2FormulatingtheApolloArchitectureDecisionProblem32614.3DecisionsandDecisionSupport33114.4FourmaintasksofDecisionSupportSystems33314.5BasicDecisionSupporttools33414.6DecisionSupportforSystemArchitecture34014.7Summary342References342reasoningaboutArchitecturaltradespaces34515.1introduction34515.2tradespaceBasics34615.3theParetoFrontier34815.4Structureofthetradespace35515.5SensitivityAnalysis35915.6OrganizingArchitecturalDecisions36415.7Summary370References371FormulatingandSolvingSystemArchitectureOptimizationProblems37316.1introduction37316.2FormulatingaSystemArchitectureOptimizationProblem37516.3NeOSSexample:AnearthObservingSatelliteSystemforNASA37716.4PatternsinSystemArchitectingDecisions37916.5FormulatingaLarge-scaleSystemArchitectureProblem40316.6SolvingSystemArchitectureOptimizationProblems40816.7Summary416References416

微服务架构(单体架构访问量)

-

,

TheshorterstartuptimesandthepossibilitytodeployMicroservicesindependentlyfromeachotherreallypayintoCI/CD.Itismuchsmootherincomparisontoregularlydeployamonolith.

EachMicroservicesisnotboundtothetechnologyusedinotherservices.Everywherewecanusethebestfittingtechnology.Olderservicescanbequicklyrewrittentousenewertechnologies.

Betterfaultisolationincomparisontothemonolithicapproach.Awelldesigneddistributedsystemwillsurvivethecrashofasingleservice.