Fitness Functions as Architectural GovernanceCode-Based Fitness FunctionsAfferent and Efferent CouplingAbstractness, Instability, and Distance from the Main SequenceDirectionality of ImportsCyclomatic Complexity and “Herding” GovernanceTurnkey ToolsLegality of Open Source LibrariesA11y and Other Supported Architecture CharacteristicsArchUnitLinters for Code GovernanceCase Study: Availability Fitness FunctionCase Study: Load-Testing Along with Canary ReleasesCase Study: What to Port?Fitness Functions You’re Already UsingIntegration ArchitectureCommunication Governance in MicroservicesCase Study: Choosing How to Implement a Fitness FunctionDevOpsEnterprise ArchitectureCase Study: Architectural Restructuring While Deploying 60 Times
per DayFidelity Fitness FunctionsFitness Functions as a Checklist, Not a StickDocumenting Fitness FunctionsSummary