Microservices make no sense. I should have stuck with the monolith.....

Building distributed systems are complicated. Documentation is poor, opinions polarised, and it takes a new way of thinking.

Building an API on top of microservices for the last three years has been a descent into madness for me.

Microservices are challenging on their own, but they get even more tricky when you throw serverless in the mix. Do I learn Kubernetes or not?

Each service needs its own database. How do I set that up? How do I stop it from getting expensive?

How do you choose what gets packaged into a service and what doesn't?

How do you make services talk to each other? If they need to communicate, why did you split them up? Do you go with an internal API or use event-driven messaging?

Let's cool the noise and learn from my failings to build scaleable microservices that are easy to set up and maintain, don't burn through hosting costs and are a joy to work with, even when the system's complexity increases. By the end of the talk, microservices will no longer be a hurdle to overcome but a helpful tool that allows you to deliver better products and outcomes to your end-users and your team.