Help Center> FunctionGraph> User Guide> Overview> How FunctionGraph Works?
View PDF

How FunctionGraph Works?

Process

Figure 1 shows the process of using functions.

  1. Write code, package and upload it to FunctionGraph, and add event sources such as Simple Message Notification (SMN), Object Storage Service (OBS), and API Gateway (APIG) event sources to build applications.
  2. Functions are triggered by RESTful API calls or event sources to achieve expected service purposes. During this process, FunctionGraph automatically schedules resources.
  3. View logs and metrics. Note that you will be billed based on code execution duration.
Figure 1 Flowchart

The following shows the details:

  1. Write code in Node.js, Python, Java, Go, C#, or PHP. For details, see the FunctionGraph Developer Guide.
  2. Edit code inline, upload a local ZIP or JAR file, or upload a ZIP file from OBS. For details, see Table 3.
  3. Functions are triggered by API calls or event sources. For details, see Using an SMN Trigger, Using a DMS Trigger, Using an APIG Trigger, Using an OBS Trigger, Using a DIS Trigger, Using a Timer Trigger, Using a CTS Trigger, Using an LTS Trigger, Using a DDS Trigger, andUsing a Kafka Trigger.
  4. FunctionGraph implements auto scaling based on the number of requests. For details about the maximum number of function instances that can be run concurrently, see Quotas and Usage Restrictions.
  5. View run logs of function as FunctionGraph is interconnected with Log Tank Service (LTS). For details, see Querying Logs.
  6. View graphical monitoring information as FunctionGraph is interconnected with Cloud Eye. For details, see Viewing Function Metrics.
  7. You will be billed based on function execution times and duration. The billing is down to the 100 ms range.
Parent topic: Overview