Let's face it... developing a proper solution for a single cloud is hard enough, so building a proper multi-cloud solution is something you can only dream of... or is it?

Each cloud is a bit different, and each cloud allows you to lock yourself into their solutions, making it difficult/expensive to even think about another cloud. But that's something you've done to yourself... the cloud only allowed you to do it, the cloud isn't the "bad guy" in this story.
To avoid these situations, you should understand what are you getting into, hopefully before you start developing.
That's why we're gonna start with some common, and some less common cloud patterns.

Once you get a general understanding of those, we'll start building a cloud solution on Azure. We're doing that because the usual path is to go with a single cloud first, but this time you're gonna learn how to properly structure the whole thing to avoid shooting yourself in the foot.

After we build something more complicated than a hello world, we'll make it yet more complicated by introducing additional regions to your solution, and all the problems which come with replicating data and thinking about consistency.
Mind you... we're still only on Azure at this point.

Once we wrap all those problems, we're gonna start introducing AWS and Google Cloud to make the whole system more resilient.
Since this will introduce a whole lot of possible problems, brace yourself, but be calm since you've built your initial system with some cloud patterns in mind 😉

As the day will come to an end, we'll have a multi-cloud system, but we won't be sure whether there's any use of it, so... what better way to end the day than doing some chaos engineering.