Why Systems Break After Initial Success: The Architectural Failures That Take Months to Surface
- Discuss this with your agent
- Open in Claude
- Open in ChatGPT
Code bugs rarely crash systems months after launch—broken architectural assumptions do. Discover how hidden physical limits trigger delayed threshold failures across databases, data lakes, and microservices.
Starting at 1:41 · Watch from the beginning
Checking access…
Playback and chapters load privately for Free videos.
Matching moments
More from World Congress 2026 Europe - Virtual Stage
Upcoming sessions on this topic
Starts in 5 days
Conference India 2026
November 25–26, 2026
Bengaluru, India
-
How We Cut Our API's p99 Latency from Minutes to Under a Second
Deepak Agrawal · Atlassian
Wed 25 Nov · Stage 2
-
A Tale of Two Systems: Design and Reality
Mandeep Singh · Kyndryl
Thu 26 Nov · Stage 1 - powered by IBM
-
Multi-Cloud Isn't a Project. It's a Side Effect.

Antonio Mendoza Pérez & Gaurav Thadani
Wed 25 Nov · Stage 3 - powered by GitHub
Related videos
Related articles
AA
Ali Alp
CH
Chris Heilmann
IK
Igor Khokhriakov
CH
Chris Heilmann
TP
Thomas Pamminger
From learning to earning
Jobs that call for the skills explored in this talk.
25 days ago
Principal Systems Engineer, Database Infrastructure
GitHub
San Francisco, CA, United States
Expert
Remote
Ruby
MySQL
Golang
15 days ago
Staff Systems Engineer, Database Infrastructure
GitHub
New York, NY, United States
Experienced
Remote
Ruby
MySQL
Golang
17 days ago
•
Software Development Engineer 1
WEX
Bengaluru, India
Starter
Hybrid · 3 days on-site
Java
Spring
17 days ago
•
Software Development Engineer 5
WEX
Bengaluru, India
Expert
Hybrid · 3 days on-site
Java
Python
Spring Boot
17 days ago
•
Software Development Engineer 1
WEX
Bengaluru, India
Starter
Hybrid · 3 days on-site
Java
9 days ago
Principal Software Engineer, Copilot Code Review
GitHub
Beverly Hills, CA, United States
Expert
Remote
Ruby
Golang
Github