SYSTEM Cited by 1 source

Tinder API Gateway (TAG)¶

TAG is Tinder's in-house API gateway platform, documented in the 2022 Tinder engineering post surfaced in the High Scalability Dec-2022 roundup.

Context¶

500+ microservices inside Tinder, communicating through a service mesh.
Tinder is deployed in 190 countries, serving global traffic patterns.
Before TAG: multiple third-party API gateways, one per application team, each on a different tech stack. Managing them across brands was unsustainable.

Architecture¶

JVM-based framework built on top of Spring Cloud Gateway.
Application teams create their own API gateway instance by writing configurations (not code).
TAG extends Spring Cloud Gateway's gateway and global filter components with pre-built filters:
Weighted routing (canary / phased rollout).
Request/response transformations.
HTTP ↔ gRPC protocol conversion (so external HTTP clients can reach internal gRPC services without the clients having to speak gRPC).
Authentication / authorization enforcement.
Rate limiting.

Multi-tenant across Match Group¶

TAG also serves the other Match Group brands:

Hinge
OkCupid
PlentyOfFish
Ship

The same gateway platform handles both B2C and B2B traffic for Tinder itself — the B2B side being partner integrations.

Why it shows up on this wiki¶

Canonical example of the configuration-as-code gateway platform model — one operator builds the gateway framework, many application teams instantiate gateways without writing code. Parallels:

patterns/graphql-unified-api-platform — Twitter's GraphQL platform serving 1.5B fields/sec across 3000 data types is the schema-unified cousin of TAG's protocol-unified gateway.

Seen in¶

sources/2022-12-02-highscalability-stuff-the-internet-says-on-scalability-for-december-2nd-2022