Building the Future Trends in Modern Application Architecture
summary
Companies are rearchitecting to chase scarce GPUs and TPUs — moving workloads between AWS, Google (for Gemini) and on‑prem — and pay attention to workload identity for nonhuman agents. Examples include fine‑grain authorization (Servos) and hybrid tunneling for sovereign data, use of Spiffy and Spire for federated workloads, and infra standards like OCI and Postgres to avoid vendor lock‑in. Teams recount a real 50 petabyte split, favor Palumi and Dagger over YAML, and choose microservices only when teams scale beyond a hundred people.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:51AI impact on app architecture
- 8:53Microservices rise and fall
- 17:05Avoiding vendor lock-in
- 21:37Database strategies for microservices
- 25:30DevOps challenges today
- 31:08Legacy apps and cloud migration
- 32:10AI, Kubernetes, microservices hype?
- 36:24Clean architecture patterns
- 40:39Prototyping vs long-term design
related talks
30mThe transformative power of modern applications
47mArchitecture and Corporate Operating Structure: a Cloud Puzzle
06mAccelerate Application Delivery with a Cloud-Native Mindset
35mBuilding large-scale Internal Developer Platforms: Core Principles
26mArchitecting for scale
52mBetting on Evolutionary Architecture
23mDesigning Robust and Scalable Distributed Applications
59mBetting on evolutionary architecture