YourAppURL

Replace the value you are getting underneath the app above.

The ultimate guide to web development interviews. Developed by FAANG engineers, practice with real-world interview questions covering network security, system design, SEO, APIs, and more.

oct6.tar.gz

server

JavaScript

Grunt

webpack

webpack-loaders

Grunt-eslint

ProgressiveRendering

webpack-code-splitting

This course compiles a comprehensive range of questions that are most likely to be asked during the frontend interview. Where many interview prep courses focus on data structures and algorithms, this course focuses on a variety of topics from network security to system design.

In this course, you will solve interview questions that cover general aspects of web development. You’ll start by going over network security and optimization techniques for load balancing and browser rendering. After that, you’ll move on to interview questions around SEO, APIs, and system design.

Overall, these are questions that are often overlooked, but they can really make you stand out from your peers. By the end of this course, you will have the confidence and ability to go in and ace that interview.

Web Development Interview Handbook

## Working with servers
Suppose you spent some time learning to code, and you developed a great website over a number of months using the best technology. It works great on your browser (localhost). It’s time to deploy it to a server. Except that the only problem is… you don’t know anything about servers or web hosting.



## The problem: provisioning servers
Suppose you have your own server with a website deployed to it. You have the necessary skills and time needed to run it.


But what happens when you only get a few visitors a day? It just sits there idle most of the time, consuming resources. This is called over-provisioning.


What if the opposite happens? What if your website goes viral and you start getting millions of visitors overnight? Your server may not be able to handle all the extra traffic! It may result in the server crashing, and the website being unavailable. This is called under-provisioning.


Also, it’s quite common for websites to have visitors during a certain time of day, month, or year, and not many at another.


## The problem: scaling

Educative, for example, usually has a lot of traffic on the weekends, when developers have time off from their day jobs to spend learning. If we needed (and this does not reflect actual numbers) 100 servers to handle the traffic on the weekends when 10 could deal with the load on weekdays, we’d have 90 servers sitting idly for 5 days a week. If (again, these are completely fake numbers) one server costs 10$ a day, we’d be spending $90 \times 5 \times 52.1429$ (weeks per year) $\approx 23,464$$ extra per year. That's a lot of money invested for servers to sit around!

## The solution: serverless

Serverless is a form of cloud computing where you don’t have to worry about servers, allowing you to focus on writing code. The term ‘serverless’ may make it seem like a server does not exist for a website, but that’s not true. It actually just means that the developer(s) won’t have to worry about the server. So, the developer won’t have to create, maintain, or deploy a server. This means that developers can focus on making a good website and not spend time building the skills to run a server. A host platform, such as Google, can take care of handling everything to do with the server.


Another benefit of serverless is that it allows for automatic scaling. So, let’s take the Educative example again. The serverless host platform would automatically scale the servers hosting the site up or down as needed.


Not only will they scale the servers automatically, but they will also only charge for the resources consumed. So, Educative would be paying more for the weekends and less for the weekdays, instead of a constant rate.


Another advantage is that you won’t have to spend time or money maintaining any servers. So, you won’t have to buy equipment, configure, or patch anything.


## Downsides
There are a few downsides that you should be aware of:

- Cost prediction can be difficult.
- You may get tied down to a certain cloud provider. Migrating to another one may require you to spend time and effort re-architecting your code.



## Serverless providers

Here’s a list of some popular serverless providers that you should be aware of:



<html>
<head>
<style>
img {
  float: left;
}
</style>
</head>
<body>


<ul>
<li><p><img src="/api/collection/10370001/6006542571667456/page/4715718955237376/image/6329739563237376" style="max-width:auto;max-height:40px;width: auto;height: auto;">
<a href="https://aws.amazon.com/lambda/">AWS Lambda</a>
</li></p>

<li><p><img src="/api/collection/10370001/6006542571667456/page/4715718955237376/image/4946235109670912" style="max-width:auto;max-height:40px;width: auto;height: auto;">
<a href="https://workers.cloudflare.com/">Cloudflare Workers</a>
</li></p>

<li><p><img src="/api/collection/10370001/6006542571667456/page/4715718955237376/image/5616966495633408" style="max-width:auto;max-height:35px;width: auto;height: auto;">
<a href="https://cloud.google.com/functions">Google Cloud Functions</a>
</li></p>

<li><p><img src="/api/collection/10370001/6006542571667456/page/4715718955237376/image/5847438962196480" style="max-width:auto;max-height:35px;width: auto;height: auto;">
<a href="https://cloud.ibm.com/functions/">IBM Cloud Functions</a>
</p>
</li>
</ul>

</body>
</html>

# Working with servers
Suppose you spent some time learning to code, and you developed a great website over a number of months using the best technology. It works great on your browser (localhost). It’s time to deploy it to a server. Except that the only problem is… you don’t know anything about servers or web hosting.



# The problem: provisioning servers
Suppose you have your own server with a website deployed to it. You have the necessary skills and time needed to run it.


But what happens when you only get a few visitors a day? It just sits there idle most of the time, consuming resources. This is called over-provisioning.


What if the opposite happens? What if your website goes viral and you start getting millions of visitors overnight? Your server may not be able to handle all the extra traffic! It may result in the server crashing, and the website being unavailable. This is called under-provisioning.


Also, it’s quite common for websites to have visitors during a certain time of day, month, or year, and not many at another.


# The problem: scaling

Educative, for example, usually has a lot of traffic on the weekends, when developers have time off from their day jobs to spend learning. If we needed (and this does not reflect actual numbers) 100 servers to handle the traffic on the weekends when 10 could deal with the load on weekdays, we’d have 90 servers sitting idly for 5 days a week. If (again, these are completely fake numbers) one server costs 10$ a day, we’d be spending $90 \times 5 \times 52.1429$ (weeks per year) $\approx 23,464$$ extra per year. That's a lot of money invested for servers to sit around!

# The solution: serverless

Serverless is a form of cloud computing where you don’t have to worry about servers, allowing you to focus on writing code. The term ‘serverless’ may make it seem like a server does not exist for a website, but that’s not true. It actually just means that the developer(s) won’t have to worry about the server. So, the developer won’t have to create, maintain, or deploy a server. This means that developers can focus on making a good website and not spend time building the skills to run a server. A host platform, such as Google, can take care of handling everything to do with the server.


Another benefit of serverless is that it allows for automatic scaling. So, let’s take the Educative example again. The serverless host platform would automatically scale the servers hosting the site up or down as needed.


Not only will they scale the servers automatically, but they will also only charge for the resources consumed. So, Educative would be paying more for the weekends and less for the weekdays, instead of a constant rate.


Another advantage is that you won’t have to spend time or money maintaining any servers. So, you won’t have to buy equipment, configure, or patch anything.


# Downsides
There are a few downsides that you should be aware of:

- Cost prediction can be difficult.
- You may get tied down to a certain cloud provider. Migrating to another one may require you to spend time and effort re-architecting your code.



# Serverless providers

Here’s a list of some popular serverless providers that you should be aware of:



<html>
<head>
<style>
img {
  float: left;
}
</style>
</head>
<body>


<ul>
<li><p><img src="/api/collection/10370001/6006542571667456/page/4715718955237376/image/6329739563237376" style="max-width:auto;max-height:40px;width: auto;height: auto;">
<a href="https://aws.amazon.com/lambda/">AWS Lambda</a>
</li></p>

<li><p><img src="/api/collection/10370001/6006542571667456/page/4715718955237376/image/4946235109670912" style="max-width:auto;max-height:40px;width: auto;height: auto;">
<a href="https://workers.cloudflare.com/">Cloudflare Workers</a>
</li></p>

<li><p><img src="/api/collection/10370001/6006542571667456/page/4715718955237376/image/5616966495633408" style="max-width:auto;max-height:35px;width: auto;height: auto;">
<a href="https://cloud.google.com/functions">Google Cloud Functions</a>
</li></p>

<li><p><img src="/api/collection/10370001/6006542571667456/page/4715718955237376/image/5847438962196480" style="max-width:auto;max-height:35px;width: auto;height: auto;">
<a href="https://cloud.ibm.com/functions/">IBM Cloud Functions</a>
</p>
</li>
</ul>

</body>
</html>

# The problem: provisioning servers
Suppose you have your own server with a website deployed to it. You have the necessary skills and time needed to run it.


But what happens when you only get a few visitors a day? It just sits there idle most of the time, consuming resources. This is called over-provisioning.


What if the opposite happens? What if your website goes viral and you start getting millions of visitors overnight? Your server may not be able to handle all the extra traffic! It may result in the server crashing, and the website being unavailable. This is called under-provisioning.


Also, it’s quite common for websites to have visitors during a certain time of day, month, or year, and not many at another.


# The problem: scaling

Educative, for example, usually has a lot of traffic on the weekends, when developers have time off from their day jobs to spend learning. If we needed (and this does not reflect actual numbers) 100 servers to handle the traffic on the weekends when 10 could deal with the load on weekdays, we’d have 90 servers sitting idly for 5 days a week. If (again, these are completely fake numbers) one server costs 10$ a day, we’d be spending $90 \times 5 \times 52.1429$ (weeks per year) $\approx 23,464$$ extra per year. That's a lot of money invested for servers to sit around!

# The solution: serverless

Serverless is a form of cloud computing where you don’t have to worry about servers, allowing you to focus on writing code. The term ‘serverless’ may make it seem like a server does not exist for a website, but that’s not true. It actually just means that the developer(s) won’t have to worry about the server. So, the developer won’t have to create, maintain, or deploy a server. This means that developers can focus on making a good website and not spend time building the skills to run a server. A host platform, such as Google, can take care of handling everything to do with the server.


Another benefit of serverless is that it allows for automatic scaling. So, let’s take the Educative example again. The serverless host platform would automatically scale the servers hosting the site up or down as needed.


Not only will they scale the servers automatically, but they will also only charge for the resources consumed. So, Educative would be paying more for the weekends and less for the weekdays, instead of a constant rate.


Another advantage is that you won’t have to spend time or money maintaining any servers. So, you won’t have to buy equipment, configure, or patch anything.


# Downsides
There are a few downsides that you should be aware of:

- Cost prediction can be difficult.
- You may get tied down to a certain cloud provider. Migrating to another one may require you to spend time and effort re-architecting your code.



# Serverless providers

Here’s a list of some popular serverless providers that you should be aware of:



<html>
<head>
<style>
img {
  float: left;
}
</style>
</head>
<body>


<ul>
<li><p><img src="/api/collection/10370001/6006542571667456/page/4715718955237376/image/6329739563237376">
<a href="https://aws.amazon.com/lambda/">AWS Lambda</a>
</li></p>

<li><p><img src="/api/collection/10370001/6006542571667456/page/4715718955237376/image/4946235109670912">
<a href="https://workers.cloudflare.com/">Cloudflare Workers</a>
</li></p>

<li><p><img src="/api/collection/10370001/6006542571667456/page/4715718955237376/image/5616966495633408">
<a href="https://cloud.google.com/functions">Google Cloud Functions</a>
</li></p>

<li><p><img src="/api/collection/10370001/6006542571667456/page/4715718955237376/image/5847438962196480">
<a href="https://cloud.ibm.com/functions/">IBM Cloud Functions</a>
</p>
</li>
</ul>

</body>
</html>

Serverless computing can greatly benefit anyone looking to focus solely on writing the best code possible for a website. Let's learn about it in this lesson.

Introduction

Network

Security

Optimizing Loading Performance

Optimizing Browser Rendering Performance

Search Engine Optimization

System Design

APIs

Testing

Version Control

Task Runners & Bundlers

Conclusion

Serverless Computing

Working with servers

The problem: provisioning servers

The problem: scaling