Chapter Eleven

API Management

The last chapter of the service catalog — two umbrella entries that hide significant complexity. Apigee and API Gateway are two different products competing for the same shelf; Firebase is an entire ecosystem on top of the GCP primitives you already know.

2 services

The chapter closes the service catalog on the two themes that ran throughout — the architecting capstone follows in Chapter 12: two products under one label (Apigee vs API Gateway, exactly the shape of the Looker vs Data Studio decision from the Data chapter) and an ecosystem layered on top of primitives (Firebase repackages Cloud Run, Firestore, Cloud Storage, and Identity Platform into a BaaS optimized for mobile and web). Both pages are about choosing deliberately rather than assuming the marketing names map onto one product each.

ApigeeFull API platform

Enterprise API programs. Developer portal, monetization, advanced policies, deep analytics. Powerful and priced accordingly. Reach for it when APIs are a product.

API GatewayLightweight front door

Simple managed gateway. An OpenAPI spec, API keys or JWT, basic rate limiting in front of Cloud Run, Functions, or App Engine. Cheap and quick.

FirebaseBaaS ecosystem

Mobile/web backend, repackaged. Auth, Firestore, Storage, Hosting, Functions, FCM over GCP primitives — optimized for time-to-market.

Services in This Chapter

Service 50

Apigee / API Gateway

Two distinct products. Apigee X is enterprise API management with developer portals, monetization, and complex policies. API Gateway is a lightweight OpenAPI-driven managed gateway. The choice between them is the chapter's central decision.

APIGateway

Service 51

Firebase

A backend-as-a-service ecosystem on top of GCP. Auth, Firestore, Hosting, Cloud Functions for Firebase, FCM, Analytics, Crashlytics — packaged for mobile and web developers. When BaaS speeds you up vs when a custom GCP stack scales better.

BaaSMobile / Web