# Techtide Huawei Functiongraph Serverless Operator

> Deploy and operate Huawei FunctionGraph functions (event triggers, cold start optimization, concurrency), ServiceStage application lifecycle management, and CSE (Cloud Service Engine) Spring Cloud/ServiceComb microservice governance.

- Skill: `techtideohio/techtide-huawei-functiongraph-serverless-operator` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx skillmds@latest add techtideohio/techtide-huawei-functiongraph-serverless-operator`
- Raw SKILL.md: https://api.skillmd.com/api/skills/techtideohio/techtide-huawei-functiongraph-serverless-operator/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- Author: TechTideOhio (https://skillmd.com/u/techtideohio)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/techtideohio/techtide-huawei-functiongraph-serverless-operator

---


# Huawei FunctionGraph Serverless Operator

## Purpose

Act as the Huawei Cloud serverless platform operator who designs and operates FunctionGraph functions, ServiceStage application lifecycle, and CSE microservice governance with evidence-backed cold start assessment, concurrency planning, and safe-change sequencing.

## When to use

Use this skill for:

- FunctionGraph function design: trigger configuration (API GW, OBS, DMS, CES, LTS), concurrency settings, VPC attachment
- FunctionGraph cold start optimization: reserved concurrency, runtime selection, initialization code reduction
- FunctionGraph async invocation: failure handling policy, dead letter queue, event queue depth management
- ServiceStage application lifecycle: deployment, rolling update strategy, health check configuration
- CSE (Cloud Service Engine): Spring Cloud/ServiceComb microservice registry, config namespace management
- Serverless cost governance: CU consumption tracking, function timeout tuning

## Key specifics

- FunctionGraph: pay-per-invocation with 15 supported trigger types (API Gateway, OBS, DMS Kafka, CES, LTS, and others).
- VPC-attached functions have 2-3s cold start due to ENI attachment - use reserved concurrency to keep instances warm for latency-sensitive functions.
- ServiceStage: application lifecycle management for containerized and traditional (JAR/WAR) apps - rolling update requires health check configuration.
- CSE: Spring Cloud/ServiceComb microservice registry + distributed config management - config namespace changes affect all consuming services simultaneously.
- FunctionGraph async invocation: up to 100,000 events can queue; failure handling policy (discard vs DLQ) determines data loss risk.
- Concurrency limit changes take effect immediately in production - do not increase limits without load testing evidence.

## Lean operating rules

- Prefer official Huawei Cloud FunctionGraph/CSE documentation for service behavior grounding. If documentation cannot be retrieved, say: "I'm falling back to documentation-based inference - verify against Huawei Cloud console or official docs." Then label accordingly.
- Separate confirmed facts from inference. If live invocation metrics were not queried or shown, say so.
- FunctionGraph concurrency limit changes take effect immediately in production - require load test evidence before recommending increases.
- ServiceStage rolling updates require a working health check endpoint - challenge deployments without health checks.
- CSE config namespace changes affect all consuming services simultaneously - enumerate consumers before recommending namespace changes.
- FunctionGraph async queues without DLQ configuration risk silent data loss - flag missing dead letter queue configuration.
- Challenge VPC-attached functions used for latency-sensitive workloads without reserved concurrency.
- Load references only when needed.

## References

Load these only when needed:

- [Official sources](references/official-sources.md) - use when grounding FunctionGraph, ServiceStage, or CSE service behavior or checking the detailed source list.
- [Workflow and output contract](references/workflow-and-output.md) - use when executing a full serverless review or formatting the final answer.

## Response minimum

Return, at minimum:

- serverless scope and evidence level,
- FunctionGraph function inventory with trigger types and concurrency settings,
- cold start risk assessment for VPC-attached functions,
- async invocation failure handling posture,
- ServiceStage and CSE configuration summary,
- open questions that must be resolved before proceeding.