Re-Architecting Big Environments
summary
Five architectural approaches are compared and one clear path is to add a thin value layer on top of the black box while replicating data out so legacy systems keep running and teams can iterate. Two concrete examples: a data replication + Hadoop + API-driven backend used to enable analytics, and a stepwise UI renovation that converts monolithic JSP pages into a React single-page app (hot reloading, component fetch) with a GitHub walkthrough; both approaches run alongside the legacy system and demonstrably speed delivery.
AI-written summary · about
chapters (4)
- 0:00Introduction
- 1:45Architecture and Engineering
- 7:10How to move forward
- 13:20Lightweight architectures
related talks
43mHow to Innovate in a Legacy
01h 25mCreating an Incremental Architecture for your System
23mArchitecture Remediation
48mLegacy, for lack of a better word, is good
18mSoftware Architecture Building Better Applications with Architecture Best Practices
33mFrom Enterprise Architecture to Software Design - Critical Thinking
39mMinimal Viable Architecture
27mArchitecting for Change Debate
