What is serverless #5 | Build a fast website | Prismic

- So, I'm here with Guillermo and for this video, I would like to go through a concrete example of Serverless, and how it would look like, and for a concrete example, for a developer. We talked about different topics and I want to have all the topics in an example. So, imagine I have an application or a website, okay? Let's say a marketing website. Well obviously, it should be fast,

care about SEO, all these kinds of things, and I would like to deploy it on Serverless. How would that look like concretely? - Yeah so typically, we integrate with any framework that already exists, whether it's Vue, React, we support and created Next.js. So with Next.js, typically, you start by creating a /pages directory. And inside that /pages directory, you sort of define all your customer facing entry points in your application.

Whether it's marketing pages, or login pages. So you could have about.js for your about page or you could have login.js for your login. So the interesting thing is when you deploy it with Serverless, what we have you do is say, hey I want use Next.js So we don't really lock you into a particularly framework. And what out platform will do is it'll take the pages directory and it'll turn each on of those into an independent serverless function. But you don't really change

the way you've been writing your application. And a long side your Next.js code for example, you could define API endpoints, you can define static pages. So it's this idea of what we call the majestic monorepo. It's a monorepo that can contain all of your customer facing logic, for serverless functions, as well as assets and static files as well as APIs. And the monorepo has this amazing advantage

that you always deploy everything at once. And because Serverless makes deployment so fast you don't really need to go around and split up your code into a hundred million places. You always just run Now, and you get your URL back. Or you Git push, and we give you your URL for your deployment. - But does it change anything if I have to call, for instance, some API for getting the content into the website? - No it's just as static or dynamic as you want.

And the really cool thing is that we deploy this to a CDN layer. So if you have static data, we can automatically cache it. If you have something that's more dynamic you can serve it on demand. And you can server render for each request. Or you can also piggy back on what we call the cache control API. So you can respond with HTTP headers to cache your content at the edge. - Right, so but still this monorepo thing

is that you have all the logic. Even if you have endpoints you will be in the same repo. - Yeah it's great. And a great example of why this is useful is companies love to have design systems or style guides. So you kind of want to have a coherent set of components for the entire company. And companies don't tend to have only one project. You log in here, and this is the entirety of my company.

They tend to want to split up their logic and their teams into sections. Sometimes into different technologies. But at the end of the day when it comes to the customer, you want to see the components and the styles all of the same. So the monorepo allows you to have components that could be shared between many different pages. Sometimes even for example you could have validation rules or Typescript types that are shared between the API