From Enterprise Architecture to Software Design - Critical Thinking
summary
Compares concrete designs and tradeoffs: a Java Spring monolith with a parent pom and modular children that can be split later, versus microservices with network latency and duplicate cross‑cutting work; a trading system benchmarks IKVM or JNI and concludes colocating processes in RAM for throughput; a middleware that stalls on a 100000‑row Excel leads to an async post-redirect-get with background Future and distributed store (Hazelcast) cutting UI wait from 5s to responsive polling (~50ms); a car‑share leak exposes refresh tokens so validate JWT issuer and apply object‑level access control are mandated; warns about third‑party risks like Log4Shell and single‑point‑of‑failure across CI, keys and proxy.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:26Mission
- 2:04Creative Process
- 2:33Architecture vs Software Design
- 4:15Monolith vs Microservices
- 4:56Pros and Cons
- 12:05Project Number 1
- 14:50Project Number 2
- 24:15Security Issues
- 28:05Common Security Issues
- 31:02Single Point of Failure
related talks
54mArchitecture Foundations: Styles & Patterns (2021)
27m“Good Enough” Architecture Part 2
48mIT Architecture : All your micro-services are wrong PERIOD!
57mSoftware Architecture: The Hard Parts
47mArchitecture Foundations: Styles & Patterns
39mSoftware is a meal best served with different architectural spices
55mUnderstanding Modern Trade-off Analysis in Software Architecture
55mArchitectural Patterns for Rapid, Reliable, Frequent and Sustainable Development