Skip to content
⌘enterprise-data-gateway.prdEN
Live2026

Enterprise Data Gateway

  1. 01// A control plane for third-party data APIs in multi-company groups: official keys held centrally, sub-keys issued in one click, with shared caching, quotas and full audit. Cache hit rate settles above 70%, cutting billed upstream calls by the same share.
  2. 02Product Owner · PRD → launch
  3. 04
  4. 05
  5. 06
  6. 07
  7. 08
  8. 09
PRD / PROTOTYPEUTF-8
https://••••••••/gw-stats
DashboardSub-keysProvidersCacheLogsAlertsHealthUsage statisticsCalls today12,480Cache hit rate87.4%Upstream calls1,572Blocked96Calls · last 24hCacheUpstream0006121824By source87%cachedCacheUpstreamBlockedQuota by subsidiarySubsidiary A82%Subsidiary B54%Subsidiary C37%Subsidiary D12%
01 / 06

Feature tour6 feature screens

70%+
steady-state cache hit rate
~70%
fewer billed upstream calls
4
subsidiaries on one-click sub-keys
60+
automated tests
Year
2026
Type
Product
Role
Product Owner · PRD → launch
Status
Live

Overview

The Enterprise Data Gateway is an API gateway for groups of companies. A group usually buys a third-party company-data service with a single official key, yet every subsidiary needs to call it — the key gets passed around, costs cannot be allocated, fields are used inconsistently and nobody can tell who made a call. The gateway keeps the official key on the group side and lets subsidiaries connect through governed sub-keys.

Results

  • Costthe first lookup of a company goes upstream and stores 5 records in the database; later lookups of that company are served from cache and never draw on the group quota. The hit rate settles above 70%, so about 70% of lookups no longer incur API fees
  • Scale4 subsidiaries across the group, each with 10–20 salespeople looking up about 10 companies a month — roughly 400–800 lookups a month, of which about 280–560 are served straight from cache
  • Speedonboarding a subsidiary goes from requesting and forwarding the official key to issuing a sub-key in one click, with permissions and quotas applied at once

Problems it solves

  • Key exposurethe official key never leaves the gateway; each subsidiary holds its own sub-key that can be disabled or rotated at any time
  • Runaway costrepeat queries are served from cache without spending official quota, and usage is allocated and reported per subsidiary
  • Inconsistent fieldseach consumer is bound to a field pack, so one source returns only the fields that business is entitled to
  • No traceabilityevery call, login and configuration change is logged

How it differs

  • Versus a generic API gateway: the group distribution model (official key → sub-keys), field packs and contract quotas are built in — no custom layer on top
  • Versus each subsidiary buying its own: one contract and one cache, with group-wide usage and cost in view
  • Four quota layerssubsidiary QPS, daily requests, group daily quota and contract total, so no single business can drain the group's allowance
  • Audit at the data layerwrites are recorded at SQL level with automatic masking, not just in application logs

Core capabilities

  • Access controlIP allowlist, request signing and per-API authorization
  • Cache warm-upbulk pre-loading of frequently queried companies, with rate limits
  • Circuit breaking & alerts: time-windowed upstream failure counting, with alerts pushed to an IM bot
  • Unified logs5 kinds — calls, logins, errors, operations and more — in one place
  • Self-monitoringone screen to tell whether the gateway, the database or the upstream is at fault
  • Quality60+ automated tests on auth, rate-limit and quota edges

Note: group and subsidiary names, the data provider, keys and call data are anonymized, and the live address is not shown.

Related notes

  1. 2026-11-08Product

    One official key, many subsidiaries — how to share it safely

    A group had one key for a third-party data service and several subsidiaries that needed it. Instead of handing it out, I put a gateway in front. Notes on the trade-offs.

    2 min read · API gateway / Key management / B2B

  2. 2026-11-03Engineering

    Five API-gateway pitfalls that look right and quietly lie to you

    What these bugs share — everything runs, the UI looks fine and the numbers are there. They are just wrong. All from an audit of my own project.

    2 min read · API gateway / Observability / Retrospective

Stack

  • Node.js
  • Fastify
  • MySQL
  • Redis
  • Vue 3
  • Element Plus
  • ECharts
  • Docker Compose
  • Nginx

Keywords

  • API gateway
  • Key management
  • Quotas & rate limits
  • Audit
  • AI-assisted dev
Up nextCorporate Site & Content PlatformA brand site and content platform for a healthcare group: an immersive chapter-based site, an AI assistant that answers only from published content, and a CMS with version rollback. AI-assisted development cut the build from 1 month to 1 week, saving CNY 30–40k.
陕ICP备2026005972号-2