Click here to watch the big shots share

What is Serverless?

Before we talk about what Serverless is, we need to talk about one of the more important architectures first. So the first structure is actually our single architecture, it is just the most original site architecture pattern, let’s say we use a single VPS as a business support for our service, then this is our single architecture. Secondly, there is our SOA architecture, which is widely used in our current enterprises. In fact, SOA is a commonly used architecture, which is to do some business separation and governance work for our complex businesses through various service modules. This is our SOA architecture.

Third is our container architecture, is quite so we better a carrier of SOA, and he is for the innovation of the underlying computing, but it is strongly dependent on its own operations an ability, because we were using the container architecture at the same time should also need a similar to the container arrangement is our CPIS arranged such a container is a tool, Or the kind of tools that we operate and maintain, we have to do some management of the nodes and so on.

So serverless architecture is actually on top of the container architecture, because it integrates all the management of the underlying resources as well as the operation and maintenance of our system. It makes it easier for our developers to use one of our zero-base facilities, which is actually our Serverless architecture.

To summarize, the Serverless architecture is a form of computing that encapsulates all of the underlying resources. Here is the original SOA. We can see that it actually has a management organization to undertake our services. In this case, we can arrange an edge of S, which has a node of a Master node. There are also a lot of Worker nodes to do containers and business orchestration.

The serverless Application is made up of two parts. The first part is our Serverless Compute Engine, which is our bottom layer. In fact, the bottom layer of Serverless in the industry is mostly Docker, of course, there are MVM based, but Docker, for example, may have something similar to open source, so Serverless actually does not refer to our Baas. So one of the other things that’s important is that in our BAAS, our baas actually has something like our API gateway, our COS, our CMQ, our Ckafka, Our CDB and a bunch of other Baas resources, so serverless is equal to our serverless plus our Baas, which is equivalent to our Serverless Compute Engine plus our SF service, Similar to a gateway, this is actually a common form of our Serverless architecture, since this is probably one of the more common resources we will use later.

Serverless front-end transformation

Let’s take a look at what Serverless can do on the front end. First I we want to know a thing is really a whole stack, I begin at the bottom by a whole stack of applications, whether he is covered with several layers of or is he need to pay attention to those things, the economic tatooine it can help us to understand what is completely stack all our serious application, under the full stack application include what the world could he be? So the bottom layer is actually something like our K8S, the bottom layer kind of container branding tool, there’s a System Security, there’s some of our rollback, there’s some of our ES, there’s some of our network Security, This is our underlying our attention more often in our pyramid or are some of the underlying resources, we care about the middle part of this is similar to one of our LB, including some of our logo we log management and so on a series of things to do some operations support to the bottom of our.

So on top of that there’s also our DB, our database, which we tend to care about a lot like our DB database, the Framework Framework, and our file storage and our CDN, which is actually an extension of some of the lower resources as a full stack application, And then finally is our serious one is the core of a development work, so our front-end developer should actually be in our top of the pyramid, it is actually ever considered this problem I write code I actually don’t need to care about what I should be a bottom, is there something you can tell me more focused to write code? Don’t care what my DB is, what our container choreography is or what we rollback we are completely? In fact, there is an answer, which is our Serverless. Therefore, the reform of our Serverless in the front-end technology is to let developers not care about all the underlying resources below our core code. We Serverless provide a complete platform like operation system or deployment platform for others to focus on their own development.

So in Serverless development mode, it’s actually very simple inside for example, our application layer should be the one that we use most often should be our API, Our BFF, our SSR, the application layer is something that we need to build by ourselves, we need to write by ourselves, and the cloud service is actually including API, SSR, our container, so the development model here is that the r&d team only needs to pay attention to the application layer, There’s also some docking of some cloud services, without having to pay attention to the lower level things like container choreography, so we can actually see in the picture above that the development team actually has a job what is it? And one of the things that he does is he actually connects things between the application layer and cloud services how do you connect things? Which brings us to our next question — do we make frames or not? Our framework we want to do this framework or how do we use this framework?

So Serverless is actually helping us to solve such a thing of the framework. It is actually divided into two parts. The first part is actually a development similar to our componentization. Our standardized relative to the second piece of content is cloud vendors some support of some of the Framework, so actually Serverless Framework it is under the advantages of can do something similar to the standardization of integration, let’s say I I may have a N under the cloud, and then to these resources to do a standardized Framework integration, So that’s doing some componentized development like a DB tool that we might talk about today, it’s actually a component of our DB, so componentized for one thing for reuse, It can improve the reuse rate of us to reduce duplication of development and stand some of the division of labor, including our staff technology including recruiting a series of some the mess of things, this is componentized significance for developers, so to standardize the simple can he is to go on some standard unified cloud vendors, It allows our business to do some smooth migration between retention including our deployment, so we can actually see in the last slide the Serverless Framework which is a standardized component-based Serverless application development product, So he used these two things of componentization and standardization to help us connect the application layer above us to the cloud service below us, So the Serverless Framework thing is essentially replacing what we provided in the first piece, which is the docking that the development team did under the traditional Serverless development model.

In this case, for the front-end, it is actually more convenient for us to do some large applications, so we can see that it is actually the Serverless Framework, which is actually composed of several pieces, the first piece is actually a Serverless application lifecycle management, It’s our CLI and our Dashboard that we’re going to launch, and it actually has some support for things like service deployment, view, rollback and some support for us to debug our logs and some support for our DevOps, and the Serverless application actually has two parts, Including our standardized framework and our component-based development, Serverless resources can be seamlessly connected to some Serverless resources of Tencent Cloud. For example, we just launched some products like TSQL. As well as some products of Serverless resources like LB that we may dock with in the future, actually these are Serverless resources. So one position I want to make clear to you is that Serverless Computing actually contains almost all the underlying resources, including our system operation and maintenance work, which makes it easier for our developers, especially our front-end developers, to use our cloud infrastructure. Serverless actually provides a way to simplify programming based on cloud resources such as switching from assembly language to high-level language. Serverless is actually a concept of a low-level secondary resource. Then there may be two layers below it. The first layer is our hairstyle, which is our SOA in a narrow sense, and our Baas, which is the collection of some surrounding cloud resources we use, similar to our SQL and COS.

The questionnaire

Tencent Cloud University is a one-stop learning and growth platform for cloud ecosystem users under Tencent Cloud. Tencent Cloud University big tycoon share invites internal technology big tycoon every week, to provide you with free, professional, the latest technology trends of the industry to share.