
Low cost of operation and maintenance
Running user code automatically, eliminating the need for user configuration or server management, helping you eliminate tedious maintenance and focus on business development and implementation.
Cloud Function
Running user code automatically, eliminating the need for user configuration or server management, helping you eliminate tedious maintenance and focus on business development and implementation.
Customers do not need to pay for idle resources or provide resources for computing and storage in advance, and only need to pay for the consumed resource when the code is running.
Cloud function can automatically scale up and down based on the amount of requests, without the need for any manual configuration. It automatically arranges reasonable computing resources based on the number of requests.
With a simple configuration, function calculations can be triggered through numerous event sources to achieve an unattended operation mode and improve the level of operation and maintenance.
Server logic
Developers use cloud functions to handle certain events when it is not suitable to write decision logic on the client, such as the lottery function, so as to ensure program security.
Statistics
Some logic requires a large amount of data, or has a high computational cost (such as certain statistical aggregation requirements), therefore it is not suitable to perform calculations on mobile clients, as it uses a lot of network data and mobile computing power.
Access third-party services
Calling a third-party API in a cloud function and using it with triggers can provide perfect access to third-party services.
To implement more complex business logics on MiniApps, such as automatic cancellation of orders, lottery and more, you only need to write a simple, single-purpose cloud function and associate it with events generated by other features (such as triggers, timed tasks).
Using cloud functions helps you complete the realization of all types of MiniApps on the market, which greatly reduces the cost of operation and maintenance. It rapidly implement features, but still has strong horizontal expansion capability.
items | unit | Pricing | description |
---|---|---|---|
Resource usage (call time) | GBs | 0.00069 Yuan/GB | The execution time is calculated from the time the code begins execution to its return or termination. The granularity of measurement is 100 milliseconds (the execution time is rounded up to the nearest 100 milliseconds. For example, if a function executes 1010 milliseconds, it will be measured as 1100 Millisecond) Take the 128 MB memory configuration as an example. After 30 seconds of execution, the resource usage = 0.128*30=3.84GBs. |
Number of calls | 10,000 times | 0.015 Yuan/1000 times | The number of calls is the total number of calls to all functions |
Public network output traffic | GB | 1 Yuan/GB | If you request external network resources in the cloud function, it will use public network. |
Other services | ReferenceOther usage charges | If you use other ifanr Cloud services in your function, you will be charged for the service, such as calling the API operation data table inside the function |
Operating environment | CPU | RAM | Disk | Number of concurrent operation |
---|---|---|---|---|
Node.js 8.9 | 0.5 core | 128 MB | 64 M | 10 |