vpruthi/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity
doc-exports/docs/fg/umn/functiongraph_02_1001.html
Chen, Junjie dac566cf2f FG UMN 20230725 version 
Reviewed-by: Eotvos, Oliver <oliver.eotvos@t-systems.com>
Co-authored-by: Chen, Junjie <chenjunjie@huawei.com>
Co-committed-by: Chen, Junjie <chenjunjie@huawei.com>
2024-04-03 10:30:56 +00:00

3.7 KiB
Raw Permalink Blame History

Event Functions

Overview

FunctionGraph supports event functions. An event can trigger function execution. Generally, it is in JSON format. You can create an event to trigger your function through the cloud service platform or CodeArts IDE Online. All types of triggers supported by FunctionGraph can trigger event functions.

  1. On the function creation page, Function Type is set to Event Function by default.
  2. During testing, a function can be triggered by simply entering the specified event in JSON format.
  3. You can also use triggers to trigger event functions.

Advantages

  • Easy single-node programming

    You can edit event functions on FunctionGraph or upload code packages there and deploy them with just a few clicks. There is no need for you to care about function concurrency or fault rectification.

  • High-performance, high-speed runtimes

    Event functions can be started, scaled, and called within milliseconds. Faults can be detected and rectified within seconds.

  • Complete tool chain

    FunctionGraph provides comprehensive logging, tracing, debugging, and monitoring, allowing developers to roll out functions in just three steps.

Restrictions

Event functions face event source restrictions. You need to comply with the function development rules of the function platform.

Parent topic: Function Types