Every Cloud Service Begins With a Problem

Pain, Problems, Solutions

Concepts appear as they come up…

Imagine you're launching a new website

00:00/01:16

1 / 1

Pain, Problems, Solutions

Certisured is an Edtech based out of Bangalore and is Co-founding team of Wizori - built to provide quick fundamental clarity in form of short vibes.

www.certisured.com

Pain, Problems, Solutions

Loading comments…

Continue your learning — your way

Sign in to unlock the full playlist, save your progress, and get a personalized feed.

Up next

Problem 2 : Computer is temporary but, Data is permanent
1:20
Problem 8: Must We Ask the Database Every Time?
1:38
Problem 5: what if demand for machines increases?
1:26
Engineering Problem 1: Renting a Computer
1:23
Problem 22: How Do We Analyze Massive Data?
1:39
Problem 7: Are Files Enough for Business?
1:45
Problem 3: Shared Object Storage
1:32
Problem 21: Where Should We Keep Our Secrets?
1:44
Problem 20: How Do Services Complete One Workflow?
1:38
Problem 6: Do We Really Need a Server?
1:29
Problem 4: Who Should Handle the Next User?
1:32
Problem 23: How Do We Query Massive Data?
1:33

Every Cloud Service Begins With a Problem — full transcript

Pain, Problems, Solutions

Pain, Problems, Solutions

Imagine you're launching a new website twenty years ago. Someone asks a simple question. "Where will your application run? " Back then, there was only one answer. Buy a physical server. That meant purchasing expensive hardware, waiting for delivery, installing it in a data center, and hoping you had bought enough computing power for the future. If your website suddenly became popular, you couldn't instantly add more capacity. And if it didn't grow as expected, you'd be left with costly hardware sitting mostly idle. This wasn't just a business problem. It was an engineering problem. How can computing become available whenever we need it, without everyone owning physical machines? Different cloud companies answered this question differently. Amazon, Microsoft and Google all built their own platforms and gave their services different names. But here's the secret. The names are temporary. The engineering problems are permanent. In this playlist, we'll first understand the engineering problem, then see how AWS, Azure and Google Cloud each solve it. Let's begin with the first question. How do you rent a computer instead of buying one?