What Is Data Architecture?Enterprise Architecture DefinedData Architecture Defined“Good” Data ArchitecturePrinciples of Good Data ArchitecturePrinciple 1: Choose Common Components WiselyPrinciple 2: Plan for FailurePrinciple 3: Architect for ScalabilityPrinciple 4: Architecture Is LeadershipPrinciple 5: Always Be ArchitectingPrinciple 6: Build Loosely Coupled SystemsPrinciple 7: Make Reversible DecisionsPrinciple 8: Prioritize SecurityPrinciple 9: Embrace FinOpsMajor Architecture ConceptsDomains and ServicesDistributed Systems, Scalability, and Designing for FailureTight Versus Loose Coupling: Tiers, Monoliths, and MicroservicesUser Access: Single Versus MultitenantEvent-Driven ArchitectureBrownfield Versus Greenfield ProjectsExamples and Types of Data ArchitectureData WarehouseData LakeConvergence, Next-Generation Data Lakes, and the Data PlatformModern Data StackLambda ArchitectureKappa ArchitectureThe Dataflow Model and Unified Batch and StreamingArchitecture for IoTData MeshOther Data Architecture ExamplesWho’s Involved with Designing a Data Architecture?ConclusionAdditional Resources
