Monoliths, microservices or something in between, regardless of our preference, for a long time now we've been building applications with multiple distributed dependencies, be them first party or third party APIs, databases, messaging systems and much, much more.

This begs the question, are we considering all the potential pitfalls when building such applications?

What happens to our precious data if there’s an hardware failure halfway through processing? How about a network hiccup? Will our API be able to handle client retries and retain consistency?

In this talk, we'll explore various ways in which things can go south, along with some ideas to navigate these challenges and build resilient systems.