Shulou(Shulou.com)05/31 Report--

Serverless developer tool example analysis, many novices are not very clear about this, in order to help you solve this problem, the following editor will explain for you in detail, people with this need can come to learn, I hope you can gain something.

A preliminary study of Serverless developer tools

Not long after the development of the Serverless architecture, a group of people signed up for the domain name of serverless.com, set up a company called Serverless, and developed a tool of the same name.

Serverless architecture and Serverless developer tools are two different things, which, if compared, are equivalent to China Telecom, referring to China's telecom industry on the one hand and Chinese telecom operators on the other.

From the name of Serverless's company, we can also infer that its products are closely related to the Serverless architecture. At a time when each cloud vendor has its own functional computing business, the Serverless team has made a tool similar to a multi-cloud management platform, which can be regarded as a multi-Serverless management tool. With this tool, you can quickly and directly use the functions of many cloud vendors, such as AWS's Lambda, Azure's Funtions and Tencent Cloud SCF, to calculate related services. Generally speaking, the supported features are as follows:

Through the above table, you can also feel that this is actually a developer tool to help users quickly use the functional services of multiple cloud vendors, packaging, deployment, rollback … Of course, various vendors have launched similar tools, such as AWS's SAM, Tencent Cloud's SCFCLI and so on.

In addition to a multi-cloud developer tool with functional computing as its core, Serverless has also launched a component tool: Components. In other words, Serverless developer tools focus not only on FaaS in Serverless, but also on BaaS, which organically integrates many back-end services and function computing, such as API gateway, object storage, CDN, database, etc., so that users can develop, deploy, update and dimension in one stop.

Serverless Framework developer tools can be split into two: Plugin and Components.

If the original Serverless Cli is more of a functional computing function of various cloud vendors in the form of Plugin, then this function called Components is more based on the overall services of each cloud vendor to help users quickly deploy the project to the Serverless architecture.

The so-called Components can be thought of as a combination of many Component. For example, if you deploy a website, you may need the following parts: static resources, function calculation, API gateway, CDN, domain name resolution, and so on. Components can help us deploy these resources in one stop, deploy static resources to object storage, and deploy function computing to functions. Deploy API gateway, CDN and other services to the corresponding products or services. If there is a need for domain name resolution, the domain name will be automatically resolved and all resources of the entire project will be associated.

In addition to one-click deployment and automatic association, Components also provides a number of solutions for deploying traditional Web frameworks to Serverless architecture. Users can deploy their existing or newly developed projects using these frameworks directly to the cloud, which is a great convenience for developers.

How do users use Plugin and Components? In fact, both functions are hosted by Serverless Cli, that is, as long as we install Serverless Framework as a developer tool, we can use both features at the same time.

The process of installing Serverless Framework developer tools is also simple:

To install Nodejs, it is officially said that nodejs only needs more than 6, but in the actual use, it is found that 6 is not good, at least 8 or more.

Install the Serverless developer tool: npm install-g serverless. After installation, you can check the version number through serverless-v to determine whether the tool has been successfully installed.

As for how to use the Serverless Framework developer tools, you can refer to the following Plugin and Components sections.

What is Serverless Plugin?

First of all, what is Plugin,Serverless Framework Plugin is actually a function management tool, using this tool, you can easily deploy functions, delete functions, trigger functions, view function information, view function logs, roll back functions, view function data, and so on.

Plugin is easy to use, and can be created directly using Serverlss Framework, for example:

Serverless create-t tencent-python-p mytest

The following figure is then generated:

Where-t refers to the template and-p refers to the path. Under Serverless Plugin operation, you can use-h in any instruction to view help information, such as viewing all instructions of Serverless Plugin. You can directly:

If you want to see Create's help:

After creating the Serverless Plugin project, we can take a look at what its Yaml looks like:

Through Yaml, we can see that it includes several major Key:Service, Provider, Plugins, and Functions from top to bottom.

Service can be thought of as a service or grouping, that is, functions under a Service can be uniformly managed, such as deploying, deleting, viewing statistics, and so on.

Provider can be considered as a scenario for defining suppliers and global variables. Here, Tencent Cloud's cloud function is used, and the provider is Tencent Cloud, so it is necessary to write tencent. At the same time, global variables can also be defined here, so that these global variables will be configured to different functions during deployment.

Plugin is the plug-in, and the Serverless team provides a huge number of Plugin, such as serverless-tencent-scf mentioned above.

Finally, there is Functions, where the function is defined.

After creating the project, writing the code, and configuring Yaml, the next step is to install Plugin:

Npm install

Use related features, such as deployment services:

Serverless deploy

When using this tool to deploy, we do not specify the account information in advance, so it will automatically evoke login by scanning the code, and continue to operate after logging in:

When the operation is completed, you will see the Service message. Note here that if you use CICD, you cannot scan the code. You must manually configure the account information in the following format:

[default] tencent_appid = appid tencent_secret_id = secretid tencent_secret_key = secretkey

After the configuration is complete, specify the file path in Yaml:

After the deployment is complete, trigger the function:

Service Information:

In addition, there are many other operations that you can try if you are interested:

Create a service

Packaged service

Deployment servic

Deployment function

Cloud call

View the log

Roll back the service

Delete a service

Get deployment list

Get service details

Get statistics

...

It should be noted that Plugin is a function developer tool that only aims at the management of function resources (except triggers), excluding API gateway, COS, database, CDN, and so on. In addition, there are only namespaces and functions in Tencent Cloud functions, but there are three-layer concepts of Service, Stage and functions in Serverless Framework Plugin. At the same time, cloud functions do not support namespaces in Plugin, so we can understand that cloud functions only have the concept of functions, while tools have three-layer concepts of services, phases and functions, which will give rise to questions: what are Service and Stage? How is it reflected in the function?

Take the hello_world we just deployed as an example:

As you can see from the figure above, Service and Stage are reflected in both the function name and the label. The function name may not be affected when it is simple to use, but when it comes to inter-function calls or cloud API using functions, it is important to note that the function name here is not the function name in Yaml!

Of course, another problem will arise here, that is, if the user already has a function and the function is not named according to a three-stage style, then there may be no way to deploy using Plugin unless the function is migrated, the original function is deleted, and the Serverless is used to redeploy.

What is Serverless Component?

Plugin is mainly about the management of functions, what about Component? Component can be thought of as a tool for cloud products, because you can combine all the components through Componnt, and you can even simply develop your own Component to meet your needs.

The Yaml of Component is segmented, while the Yaml of Plugin is a whole. There may be no relationship between the two components in Component, for example:

Test1: component: "@ gosls/tencent-website" inputs: code: src:. / public index: index.html error: index.html region: ap-shanghai bucketName: test1 test2: component: "@ gosls/tencent-website" inputs: code: src:. / public index: index.html error: index.html region: ap-shanghai bucketName: test2

Through Yaml we can see that the whole code can be divided into two parts, is to put the code of a website on a different Bucket.

Currently, the basic components of Tencent Cloud Component include:

@ serverless/tencnet-scf@serverless/tencnet-cos@serverless/tencnet-cdn@serverless/tencnet-apigateway@serverless/tencnet-cam-role@serverless/tencnet-cam-policy

The encapsulated upper layer Component includes:

@ serverless/tencnet-express@serverless/tencnet-bottle@serverless/tencnet-django@serverless/tencnet-egg@serverless/tencnet-fastify@serverless/tencnet-flask@serverless/tencnet-koa@serverless/tencnet-laravel@serverless/tencnet-php-slim@serverless/tencnet-pyramid@serverless/tencnet-tornado@serverless/tencnet-website

Basic Component means that relevant resources can be deployed through the relevant Component, for example, tencent-scf can deploy cloud functions, and tencent-cos can deploy a bucket. The Component in the upper layer is actually a combination of the underlying Component, and some additional logic is added to achieve some high-level functions. For example, tencent-django can deploy the Django framework to the cloud function through the WSGI conversion of the request, and the bottom layer relies on components such as tencent-scf/tencent-apigateway.

Component doesn't have that many operations compared to Plugin, only two: deploy and remove.

For example, a deployment operation:

Serverless-debug

Remove operation:

Serverless remove-debug

Compared with Plugin, the product latitude of Component is increased, but the actual number of features is reduced. However, this is not a big problem, after all, Plugin can be mixed with Component, the real problem that needs to be solved is, the Yaml of the two is different, how to mix?

Functions deployed online by Plugin will automatically change their names. For example, if the function is myFunction and the service and phase are myService-Dev, then the function deployed online is myService-Dev-myFunction. Such a function name may cause many uncontrollable factors in inter-function calls: if the environment is Dev, the inter-function calls should be named myService-Dev-myFunction. If the environment is Test, write myService-Test-myFunction at this time. In my opinion, environment changes only need to change the configuration, there is no need to change more in-depth code logic, so this makes me feel unfriendly

Plugin also has advantages, for example, if there is Invoke, Remove and the ability to deploy a single function, while Plugin also has global variables, it is like a developer tool that can develop, deploy, call, view information, metrics, delete rollbacks and other operations

Components can be seen as a set of components, which includes a lot of Components, basic Components, such as cos, scf, apigateway, etc., as well as some extended Components, such as website extended on cos, static websites can be deployed directly, and some framework-level ones, such as Koa,Express

In addition to supporting many products and deploying frameworks, Components is most attractive to me because the name of the function it deploys online is the specified name, and there will be nothing extra.

Components is a little thinner than Plugin in terms of functionality, with no other features except deployment and deletion. When you need to deploy multiple things and write them on the yaml of a Components, even if you modify only one function, it needs to be redeployed all over again

Components is more defined as a component, so there are no global variables in Components.

Is it helpful for you to read the above content? If you want to know more about the relevant knowledge or read more related articles, please follow the industry information channel, thank you for your support.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.