Charting a Course Through Enterprise Architecture
summary
Panel argues Enterprise architecture moves from diagrams to experiments: companies build an Enterprise Data Hub (one unified store, often Hadoop) to give everyone the same truth; prototypes get built fast and then deliberately thrown away — throwaway prototype — before full implementation; successful microservice stacks mandate microservices require own persistence, service-level agreements and chargeback so teams optimize usage. Examples: human genome is ~3 billion bases (≈0.5 TB per genome), ovarian chemo choices lack guidance, and cost-allocation cut one team’s resource use dramatically.
AI-written summary · about
chapters (5)
- 0:00Start
- 27:48Embracing the Cloud (The Obvious) Provisioning Speed
- 31:17Embracing the Cloud (The Less Obvious) Instance Optimization Opportunities
- 33:52So You Still Want Your Own Data Center ... Unstoppable Economics
- 59:26The Monolithic Architecture
related talks
50mEnterprise Architecture = Architecting the Enterprise
43mModern Enterprise Architecture: architecting for outcomes "Modern Enterprise A..."
38mModern Enterprise Architecture: Architecting for Outcomes
37mThe Dark Gods of Enterprise Architecture. To Warp and Back
40mIs it possible for enterprise architects to be really agile?
28mThe lean architect: Experimenting your way to better decisions
33mFrom Enterprise Architecture to Software Design - Critical Thinking
58mEffective Architecture Practices Debate