Problems Before Products
Problems Before Products
Imagine you're building a new application. The software is ready. The design looks great. The team is excited. Then someone asks a simple question. "Where will your application actually run? " Twenty years ago, the answer was simple. Buy a server. A real physical machine. You had to purchase it, wait for it to arrive, install it in a data center, configure it, power it, secure it and maintain it. Now imagine your application suddenly becomes popular. Thousands of users arrive overnight. Your server isn't powerful enough. You need another one. But hardware cannot be purchased in minutes. It takes days... sometimes weeks. So companies bought larger servers hoping they would be enough in the future. Sometimes they guessed right. Often, they paid for expensive machines that remained mostly unused. This wasn't a problem unique to Amazon. Or Microsoft. Or Google. It was a universal engineering problem. Every cloud platform that exists today is simply a collection of solutions to problems like these. So in this playlist, we're not going to memorize product names. We'll first understand the problem. Then we'll understand the concept that solved it. Finally, we'll see what Amazon Web Services, Microsoft Azure and Google Cloud chose to call that solution. Because names change. Problems don't. And our first problem is this... How do you use a computer without buying one?