forked from docs/doc-exports
liusiying01
904c1aad8b
Reviewed-by: Mützel, Andrea <andrea.muetzel@t-systems.com> Co-authored-by: liusiying01 <liusiying@huawei.com> Co-committed-by: liusiying01 <liusiying@huawei.com>
43 lines
5.3 KiB
HTML
43 lines
5.3 KiB
HTML
<a name="functiongraph_02_1005"></a><a name="functiongraph_02_1005"></a>
|
|
|
|
<h1 class="topictitle1">Concepts</h1>
|
|
<div id="body0000001212443732"><div class="section" id="functiongraph_02_1005__section4880412123"><h4 class="sectiontitle">Function</h4><p id="functiongraph_02_1005__p1443142071918">Functions are code defined to handle events.</p>
|
|
</div>
|
|
<div class="section" id="functiongraph_02_1005__section15855142131814"><h4 class="sectiontitle">Event Source</h4><p id="functiongraph_02_1005__p5458154461918">An event source is a public cloud service or custom application that publishes events.</p>
|
|
</div>
|
|
<div class="section" id="functiongraph_02_1005__section580315715405"><h4 class="sectiontitle">Runtime</h4><p id="functiongraph_02_1005__p10491185917409">The runtime provides an execution environment for the corresponding programming language to pass function invocation events, context information, and responses.</p>
|
|
<p id="functiongraph_02_1005__p63591696291">FunctionGraph currently supports Node.js, Python, Java, Go, C#, PHP, and custom runtimes.</p>
|
|
</div>
|
|
<div class="section" id="functiongraph_02_1005__section12316118171810"><h4 class="sectiontitle">Synchronous Invocation</h4><p id="functiongraph_02_1005__p10305172313200">Clients wait for explicit responses to their requests from a function. Responses are returned only after the function is invoked.</p>
|
|
</div>
|
|
<div class="section" id="functiongraph_02_1005__section135316214188"><h4 class="sectiontitle">Asynchronous Invocation</h4><p id="functiongraph_02_1005__p5258154372017">Clients do not care about the function invocation results of their requests. After receiving a request, FunctionGraph puts it in a queue, returns a response, and processes other requests when there are idle resources.</p>
|
|
</div>
|
|
<div class="section" id="functiongraph_02_1005__section623011274184"><h4 class="sectiontitle">Trigger</h4><p id="functiongraph_02_1005__p18474752192015">A trigger is an event that triggers function execution. Triggers can also be used to trigger functions when specified cloud service events occur.</p>
|
|
</div>
|
|
<div class="section" id="functiongraph_02_1005__section1265336171815"><h4 class="sectiontitle">Single-Instance Multi-Concurrency</h4><p id="functiongraph_02_1005__p8159142152218">The number of requests that can be concurrently processed by an instance.</p>
|
|
</div>
|
|
<div class="section" id="functiongraph_02_1005__section19972043131820"><h4 class="sectiontitle">Custom Images</h4><p id="functiongraph_02_1005__p12169174793110">You can directly package and upload container images. The platform then loads and starts these images to create functions.</p>
|
|
</div>
|
|
<div class="section" id="functiongraph_02_1005__section12272114871818"><h4 class="sectiontitle">Custom Function Execution</h4><p id="functiongraph_02_1005__p116023118317">You can customize scripts and files to execute functions.</p>
|
|
</div>
|
|
<div class="section" id="functiongraph_02_1005__section6578125291812"><h4 class="sectiontitle">Function Logs</h4><p id="functiongraph_02_1005__p423936193118">Logs generated during function invocation.</p>
|
|
</div>
|
|
<div class="section" id="functiongraph_02_1005__section683195814186"><h4 class="sectiontitle">Function Monitoring</h4><p id="functiongraph_02_1005__p54611513118">Monitoring information generated during function execution.</p>
|
|
</div>
|
|
<div class="section" id="functiongraph_02_1005__section15113220197"><h4 class="sectiontitle">Function Version</h4><p id="functiongraph_02_1005__p1368711526263">FunctionGraph allows you to publish one or more versions throughout the development, testing, and production processes to manage your function code. The code and environment variables of each version are saved as a snapshot. After the function code is published, modify settings when necessary.</p>
|
|
</div>
|
|
<div class="section" id="functiongraph_02_1005__section36774610194"><h4 class="sectiontitle">Function Alias</h4><p id="functiongraph_02_1005__p4688195272612">You can create an alias for a specific function version. To roll back to a previous version, use the corresponding alias to represent the version instead of modifying the function code.</p>
|
|
<p id="functiongraph_02_1005__p682761715276">Each function alias can be bound to a major version and an additional version for traffic shifting.</p>
|
|
</div>
|
|
<div class="section" id="functiongraph_02_1005__section779517105197"><h4 class="sectiontitle">Dependency Package</h4><p id="functiongraph_02_1005__p451915112275">A dependency contains public libraries that support the running of function code. You can encapsulate the required public libraries into a dependency for easier management, sharing, and smaller deployment sizes.</p>
|
|
</div>
|
|
<div class="section" id="functiongraph_02_1005__section12609104354011"><h4 class="sectiontitle">Bootstrap File</h4><p id="functiongraph_02_1005__p18338202818811">The <strong id="functiongraph_02_1005__b1834061110339">bootstrap</strong> file is the startup file of an HTTP function. The HTTP function can only read <strong id="functiongraph_02_1005__b134611114333">bootstrap</strong> as the startup file name. If the file name is not <strong id="functiongraph_02_1005__b834717113334">bootstrap</strong>, the service cannot be started.</p>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="functiongraph_01_1000.html">Service Overview</a></div>
|
|
</div>
|
|
</div>
|
|
|