Cloud Functions Update
서버 관리에 대한 부담 없이 손쉽게 원하는 비즈니스 로직을 실행할 수 있습니다.
Use Less Time on Server Management and Focus on Code Execution and Computing Time
With Cloud Functions, you can spend more time on writing business logic codes without additional tasks for server scalability or management.
Efficiently operate your service on a pay-as-you-go rate.
- No Burden of Server Management
- There is no need for server provisioning or managing. You can simply register the codes you have written as actions to the Cloud Functions for easy execution.
- Faster Development
- You can enjoy an improved development speed and focus on developing the business logic as there is no need for server provisioning. Any modifications in the codes of action are applied instantly.
- On-demand Execution
- There is no need to worry about scaling out. The same number of code executions as the request is guaranteed at all times. This helps you reduce costs for code execution when there is no request.
- Various Operating Methods
- Link with the Cloud Functions to create a range of services. You can build a serverless backend to process various types of API requests such as those used by mobile, web, and IoT applications. We are also planning to link to other NAVER CLOUD PLATFORM services in the future.
Detailed Features
You can simply register the codes you have written as actions to the Cloud Functions for easy execution.
In the future, the function will be extended so that the code written with various NAVER CLOUD PLATFORM services can work.
(You can build various types of serverless environment such as backend, real time and IoT by triggering NAVER CLOUD PLATFORM services such as Object Storage, CLA, Simple & Easy Notification Service and Monitoring.)
Action
An action is a stateless code fragment that carries out a specific job. Actions can be written in JavaScript, Swift, Java, Python, and PHP. An example of an action would be: detecting user's images, responding to a change in the database, or aggregating a set of API calls. Actions may be called by a user, executed in response to an event, or may be executed as a sequence by receiving a result of another action as input.
Trigger
A"Trigger" is an event delivery object that can receive events from cloud services or external services that is compatible with Cloud Functions to execute "action". When an event occurs, triggers can run one or more actions in parallel, depending on the event that you have registered. The data from the events delivered when the trigger is executed is delivered to the execution parameters of each individual action.
Web Action
You can create a web-based application program using a web action. Through this, you can implement backend logic so your web application can access anonymously without the need for an authentication key. However, you must implement directly within the action if you need functions, such as authentication or OAuth.
Package
A package is a unit of sharing actions and feeds. You can use the package to manage relevant actions and feeds as one and even share it with others. Convenient shared packages are provided in Cloud Functions.
Related Services
Pricing Information
Cloud Functions is ideal for high usage due to its scaling capability for parallel requests.
Usage Fee
In Cloud Functions
- Request: Fees are charged based on the total number of requests.
- Time taken: Time taken is calculated based on the time the code started execution until the time it was returned or terminated. It is rounded up by a maximum of 100 ms units. Fees vary depending on the amount of memory allocated to the function. (Fees will be charged per second as gigabyte memory units.)
| (Execution) Request | (Computing Usage) Elapsed times |
|---|---|
| [Free Tier] Free request up to 1 million times a month 200 KRW per million request over the free tier | [Free Tier] Free 400,000 GB-seconds per month 0.017 KRW for every GB-second usage over free tier * Fees depend on the amount of memory allocated to the function. |
* You can approximately estimate monthly charges with action execution times, allocated memory, and number of monthly execution.
- Average execution time : 500 (millisecond) / Action Memory: 128 (MB) / Number of monthly requests: 5,000,000 (time)
= Monthly charges: total of 800 KRW Computing Usage
Average execution time : 500 (millisecond)
Action Memory: 128 (MB)
Number of monthly requests: 5,000,000 (time)Total computing time (average execution time * number of monthly requests) : 2,500,000 (second)
Total computing time (total computing time * action memory / GB) : 312,500 (GB-sec)
Free tier (month): 400,000 (GB-sec)
Computing usage to be charged : 0Execution request
Number of monthly requests: 5,000,000 times
Free tier (month): 1,000,000 (time)
Number of requests to be charged: 4,000,000 timesCalculation of Service Charges
Computing usage charges: 0 KRW
Request usage charges: 800 KRW
- Average execution time : 500 (millisecond) / Action Memory: 256 (MB) / Number of monthly requests: 5,000,000 (time)
= Monthly Charges: Total of 4,625 KRW Computing Usage
Average execution time : 500 (millisecond)
Action Memory: 256 (MB)
Number of monthly requests: 5,000,000 (time)Total computing time (average execution time * number of monthly requests) : 2,500,000 (second)
Total computing time (total computing time * action memory / GB): 625,000 (GB-second)
Free tier(month): 400,000 (GB-sec)
Computing usage to be charged: 225,000 (GB-sec)Execution Request
Number of monthly requests: 5,000,000 (time)
Free tier (month): 1,000,000 (time)
Number of requests to be charged: 4,000,000 (time)Calculation of Service Charges
Computing usage (Computing usage to be charged(GB-sec) * 0.017 won) : 3,825 KRW (225,000 * 0.017)
Request usage charges: 800 KRW
Was this page helpful?