Problem 6: Do We Really Need a Server?

Code Without Servers

Concepts appear as they come up…

So far, every problem has been

00:00/01:28

1 / 1

Code Without Servers

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

Code Without Servers

Loading comments…

Continue your learning — your way

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

Up next

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

Problem 6: Do We Really Need a Server? — full transcript

Code Without Servers

Code Without Servers

So far, every problem has been solved by creating more virtual machines. Need more computing? Launch another server. Need more capacity? Launch even more servers. But engineers noticed something interesting. Many applications didn't need a server running all day. For example, a customer uploads a profile picture. The application simply resizes the image. The task takes only a few seconds. Yet an entire virtual machine remains running twenty-four hours a day, waiting for the next upload. The engineering problem became obvious. Do we really need an entire server just to execute a small piece of code? The engineering concept that solved this problem is Serverless Computing, also known as Function as a Service (FaaS). Instead of managing virtual machines, developers simply upload their code. The cloud automatically runs it whenever an event occurs, scales it as needed, and stops when the work is complete. Amazon Web Services calls this AWS Lambda. Microsoft Azure calls it Azure Functions. Google Cloud calls it Cloud Functions. Different names. One engineering concept. Now developers focused on writing code instead of managing servers. But applications still had another challenge. Where should we store structured business data like customers, orders and transactions?