You've gone through your mid-2010's cloud migration and things are not ok.

Your system is flakey, teams in conflict, and errors transient and temperamental - where did it all go wrong?

In this session, we discuss what being "cloud native" really means, distinct from vendor hype, and middleware sales pitch, covering cloud architectural patterns that make your software resilient in the real world, not just on paper.

The work doesn't stop at the platform - it starts with you.

This is a session about:

- Graceful degradation
- Bulkheading
- Circuit Breaking
- Designing for Failure
- Data replication
- Running partially offline