Cloud Native 10 min read

How Higress Serverless Enterprise Cuts Costs 90% and Boosts Auth Performance 30×

A SaaS platform’s consumer count surged from 200 to nearly 20,000, causing open‑source Higress authentication latency to jump 34‑fold and configuration size to balloon 8,457‑fold, while a local comparative test shows the Higress Enterprise Serverless edition maintains sub‑2 ms latency, 100 % success, tiny config footprints, and up to 90 % lower annual costs.

Alibaba Cloud Native
Alibaba Cloud Native
Alibaba Cloud Native
How Higress Serverless Enterprise Cuts Costs 90% and Boosts Auth Performance 30×

Background: a SaaS platform’s infrastructure grew from 200 to about 20,000 API consumers, causing authentication latency to rise from 1 ms p50 to over 50 ms and configuration size to swell dramatically.

Problem: as consumer numbers scale, the authentication chain must keep low latency, high success rate, and controllable configuration cost.

Method: local comparative tests were run between the open‑source self‑built Higress and Alibaba Cloud’s Cloud‑Native API Gateway (Higress Enterprise Serverless). Both used identical runtime, upstream services, and request model, testing consumer counts of 10, 100, 500, 1 000, 5 000, 10 000 and 20 000 with a fixed QPS of 10 for 20 seconds each.

Results:

Latency: at 10 k consumers, enterprise p50 = 1.47 ms versus open‑source 50.32 ms (≈34× slower).

Success rate: at 20 k consumers, enterprise maintained 100 % success while open‑source dropped to 77.14 % (a 22.86‑percentage‑point decline).

Configuration size: at 20 k consumers, enterprise config was 149 B versus open‑source 1.23 MB (≈8 457× larger).

Analysis: the enterprise version decouples consumer scale from the authentication path, keeping per‑request auth cost constant, separating consumer data from execution configuration, and preventing linear growth of plugin configuration. This design yields stable performance even when consumers reach hundreds of thousands.

Cost comparison: a minimal self‑built deployment (2 × 2C4G ECS, NLB, EIP) costs roughly 5 241 CNY per year regardless of traffic. The Serverless edition charges a fixed instance fee plus tiered usage; for 1 M daily calls the annual cost is about 1 945 CNY, a 37 % reduction versus self‑hosted. Across call volumes, Serverless saves 70‑90 % for small users and 30‑50 % for large users.

Conclusion: migrating to Higress Enterprise Serverless provides substantial latency, reliability, configuration‑size, and cost benefits, making it a high‑value upgrade for teams using or planning to use Higress.

Original Source

Signed-in readers can open the original source through BestHub's protected redirect.

Sign in to view source
Republication Notice

This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactadmin@besthub.devand we will review it promptly.

performanceCloud NativeServerlessAPI GatewayCost OptimizationHigress
Alibaba Cloud Native
Written by

Alibaba Cloud Native

We publish cloud-native tech news, curate in-depth content, host regular events and live streams, and share Alibaba product and user case studies. Join us to explore and share the cloud-native insights you need.

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.