book

Fundamentals of Software Architecture

Name: Fundamentals of Software Architecture
ISBN: 9781492043454

by Mark Richards, Neal Ford

January 2020

Beginner

432 pages

11h 26m

English

O'Reilly Media, Inc.

Audiobook available

Read now

Unlock full access

Preface: Invalidating Axioms
Conventions Used in This BookSupplemental MaterialO’Reilly Online LearningHow to Contact UsAcknowledgmentsAcknowledgments from Mark RichardsAcknowledgments from Neal Ford
1. Introduction
Defining Software ArchitectureExpectations of an ArchitectMake Architecture DecisionsContinually Analyze the ArchitectureKeep Current with Latest TrendsEnsure Compliance with DecisionsDiverse Exposure and ExperienceHave Business Domain KnowledgePossess Interpersonal SkillsUnderstand and Navigate PoliticsIntersection of Architecture and…Engineering PracticesOperations/DevOpsProcessDataLaws of Software Architecture
I. Foundations
2. Architectural Thinking
Architecture Versus DesignTechnical BreadthAnalyzing Trade-OffsUnderstanding Business DriversBalancing Architecture and Hands-On Coding
3. Modularity
DefinitionMeasuring ModularityCohesionCouplingAbstractness, Instability, and Distance from the Main SequenceDistance from the Main SequenceConnascenceUnifying Coupling and Connascence MetricsFrom Modules to Components
4. Architecture Characteristics Defined
Architectural Characteristics (Partially) ListedOperational Architecture CharacteristicsStructural Architecture CharacteristicsCross-Cutting Architecture CharacteristicsTrade-Offs and Least Worst Architecture
5. Identifying Architectural Characteristics
Extracting Architecture Characteristics from Domain ConcernsExtracting Architecture Characteristics from RequirementsCase Study: Silicon SandwichesExplicit CharacteristicsImplicit Characteristics
6. Measuring and Governing Architecture Characteristics
Measuring Architecture CharacteristicsOperational MeasuresStructural MeasuresProcess MeasuresGovernance and Fitness FunctionsGoverning Architecture CharacteristicsFitness Functions
7. Scope of Architecture Characteristics
Coupling and ConnascenceArchitectural Quanta and GranularityCase Study: Going, Going, Gone
8. Component-Based Thinking
Component ScopeArchitect RoleArchitecture PartitioningCase Study: Silicon Sandwiches: PartitioningDeveloper RoleComponent Identification FlowIdentifying Initial ComponentsAssign Requirements to ComponentsAnalyze Roles and ResponsibilitiesAnalyze Architecture CharacteristicsRestructure ComponentsComponent GranularityComponent DesignDiscovering ComponentsCase Study: Going, Going, Gone: Discovering ComponentsArchitecture Quantum Redux: Choosing Between Monolithic Versus Distributed Architectures

II. Architecture Styles
9. Foundations
Fundamental PatternsBig Ball of MudUnitary ArchitectureClient/ServerMonolithic Versus Distributed ArchitecturesFallacy #1: The Network Is ReliableFallacy #2: Latency Is ZeroFallacy #3: Bandwidth Is InfiniteFallacy #4: The Network Is SecureFallacy #5: The Topology Never ChangesFallacy #6: There Is Only One AdministratorFallacy #7: Transport Cost Is ZeroFallacy #8: The Network Is HomogeneousOther Distributed Considerations
10. Layered Architecture Style
TopologyLayers of IsolationAdding LayersOther ConsiderationsWhy Use This Architecture StyleArchitecture Characteristics Ratings
11. Pipeline Architecture Style
TopologyPipesFiltersExampleArchitecture Characteristics Ratings
12. Microkernel Architecture Style
TopologyCore SystemPlug-In ComponentsRegistryContractsExamples and Use CasesArchitecture Characteristics Ratings
13. Service-Based Architecture Style
TopologyTopology VariantsService Design and GranularityDatabase PartitioningExample ArchitectureArchitecture Characteristics RatingsWhen to Use This Architecture Style
14. Event-Driven Architecture Style
TopologyBroker TopologyMediator TopologyAsynchronous CapabilitiesError HandlingPreventing Data LossBroadcast CapabilitiesRequest-ReplyChoosing Between Request-Based and Event-BasedHybrid Event-Driven ArchitecturesArchitecture Characteristics Ratings
15. Space-Based Architecture Style
General TopologyProcessing UnitVirtualized MiddlewareData PumpsData WritersData ReadersData CollisionsCloud Versus On-Premises ImplementationsReplicated Versus Distributed CachingNear-Cache ConsiderationsImplementation ExamplesConcert Ticketing SystemOnline Auction SystemArchitecture Characteristics Ratings
16. Orchestration-Driven Service-Oriented Architecture
History and PhilosophyTopologyTaxonomyBusiness ServicesEnterprise ServicesApplication ServicesInfrastructure ServicesOrchestration EngineMessage FlowReuse…and CouplingArchitecture Characteristics Ratings
17. Microservices Architecture
HistoryTopologyDistributedBounded ContextGranularityData IsolationAPI LayerOperational ReuseFrontendsCommunicationChoreography and OrchestrationTransactions and SagasArchitecture Characteristics RatingsAdditional References
18. Choosing the Appropriate Architecture Style
Shifting “Fashion” in ArchitectureDecision CriteriaMonolith Case Study: Silicon SandwichesModular MonolithMicrokernelDistributed Case Study: Going, Going, Gone
III. Techniques and Soft Skills
19. Architecture Decisions
Architecture Decision Anti-PatternsCovering Your Assets Anti-PatternGroundhog Day Anti-PatternEmail-Driven Architecture Anti-PatternArchitecturally SignificantArchitecture Decision RecordsBasic StructureStoring ADRsADRs as DocumentationUsing ADRs for StandardsExample
20. Analyzing Architecture Risk
Risk MatrixRisk AssessmentsRisk StormingIdentificationConsensusAgile Story Risk AnalysisRisk Storming ExamplesAvailabilityElasticitySecurity
21. Diagramming and Presenting Architecture
DiagrammingToolsDiagramming Standards: UML, C4, and ArchiMateDiagram GuidelinesPresentingManipulating TimeIncremental BuildsInfodecks Versus PresentationsSlides Are Half of the StoryInvisibility
22. Making Teams Effective
Team BoundariesArchitect PersonalitiesControl FreakArmchair ArchitectEffective ArchitectHow Much Control?Team Warning SignsLeveraging ChecklistsDeveloper Code Completion ChecklistUnit and Functional Testing ChecklistSoftware Release ChecklistProviding GuidanceSummary
23. Negotiation and Leadership Skills
Negotiation and FacilitationNegotiating with Business StakeholdersNegotiating with Other ArchitectsNegotiating with DevelopersThe Software Architect as a LeaderThe 4 C’s of ArchitectureBe Pragmatic, Yet VisionaryLeading Teams by ExampleIntegrating with the Development TeamSummary
24. Developing a Career Path
The 20-Minute RuleDeveloping a Personal RadarThe ThoughtWorks Technology RadarOpen Source Visualization BitsUsing Social MediaParting Words of Advice
Self-Assessment Questions
Chapter 1: IntroductionChapter 2: Architectural ThinkingChapter 3: ModularityChapter 4: Architecture Characteristics DefinedChapter 5: Identifying Architecture CharacteristicsChapter 6: Measuring and Governing Architecture CharacteristicsChapter 7: Scope of Architecture CharacteristicsChapter 8: Component-Based ThinkingChapter 9: Architecture StylesChapter 10: Layered Architecture StyleChapter 11: Pipeline ArchitectureChapter 12: Microkernel ArchitectureChapter 13: Service-Based ArchitectureChapter 14: Event-Driven Architecture StyleChapter 15: Space-Based ArchitectureChapter 16: Orchestration-Driven Service-Oriented ArchitectureChapter 17: Microservices ArchitectureChapter 18: Choosing the Appropriate Architecture StyleChapter 19: Architecture DecisionsChapter 20: Analyzing Architecture RiskChapter 21: Diagramming and Presenting ArchitectureChapter 22: Making Teams EffectiveChapter 23: Negotiation and Leadership SkillsChapter 24: Developing a Career Path
Index
About the Authors

404

Not Found

Either this content does not exist or you do not have access to it. Try searching for something new.

Cloud Computing

Data Engineering

Data Science

AI & ML

Programming Languages

Software Architecture

IT/Ops

Security

Design

Business

Soft Skills

Fundamentals of Software Architecture

by Mark Richards, Neal Ford

404

Not Found