FaaS Platform
VNETWORK Cloud Functions — a custom Kubernetes-native, multi-tenant Function-as-a-Service platform. Phase 1 complete with measured throughput; Phase 2 in progress.
Why
VNETWORK Cloud needs a multi-tenant Function-as-a-Service it fully owns, and the obvious off-the-shelf options do not fit. OpenFaaS Community Edition leaves scale-to-zero behind a paid Pro license and offers only basic multi-tenancy, which means depending on OpenFaaS Ltd’s pricing to sell the product. Knative is Apache 2.0 but ships a heavy control plane — its controllers plus a Kourier ingress cost roughly 1 GB RAM against the custom platform’s ~400 MB — with no built-in async invocation and no built-in multi-tenancy. A custom platform composed from CNCF building blocks (KEDA, NATS JetStream, Capsule, all Apache 2.0) keeps full control, carries no commercial license, and integrates directly with the surrounding VNETWORK ecosystem.
Architecture
A request terminates TLS at the dedicated Ingress and reaches the Gateway, which resolves the tenant, authenticates, and applies rate limits before invoking the target function over HTTP or WebSocket. The Operator watches Function custom resources and provisions each tenant’s Deployment, Service, and KEDA ScaledObject; KEDA scales functions to zero and back on request rate or NATS JetStream queue depth. Capsule bounds every tenant namespace with its own ResourceQuota and NetworkPolicy.
Phase 1 — measured
375 RPS
1656 msg/sec WebSocket throughput
Phase 1 is complete with these measurements.
Phase 2
In progress. The Phase 1 / Phase 2 distinction is kept explicit — Phase 2 capability is not presented as already shipped.
Status
Building (Phase 1 delivered, Phase 2 in progress).