API / APIGEE Gateway Interview Questions
What is the Apigee hybrid architecture in more depth, including its components?
Apigee hybrid splits responsibilities between Google-managed and customer-managed infrastructure. Understanding the component split is important for architects and operations engineers.
| Component | Where it runs | Managed by |
|---|---|---|
| Management Plane (UI, API, analytics ingestion) | Google Cloud | |
| Apigee Connect | Customer's Kubernetes cluster | Customer (installed by Google tooling) |
| Message Processor (proxy runtime) | Customer's Kubernetes cluster | Customer (installed by Helm/Apigee Operator) |
| Cassandra (config/KVM storage) | Customer's Kubernetes cluster | Customer |
| Mart (API metadata service) | Customer's Kubernetes cluster | Customer |
| Synchroniser | Customer's Kubernetes cluster | Customer - syncs config from management plane |
| UDCA (Universal Data Collection Agent) | Customer's Kubernetes cluster | Customer - ships analytics to Google |
# Apigee hybrid installation summary (Kubernetes-based) # Prerequisites: # - GKE (or any CNCF-certified Kubernetes cluster) # - cert-manager installed # - Anthos Service Mesh (optional but recommended) # Install via Apigee Operator (Helm chart): helm install apigee-operator \ oci://us-docker.pkg.dev/apigee-release/apigee-operators/apigee-operators \ --namespace apigee-system # Apply the ApigeeOrganization and ApigeeEnvironment CRDs: kubectl apply -f apigee-org.yaml kubectl apply -f apigee-env.yaml # Key hybrid release (mid-2026): # Apigee hybrid v1.14.6 (released June 16, 2026) # Apigee instance runtime 1-17-0-apigee-9
The Synchroniser is a critical component that periodically polls the management plane and downloads the latest proxy configurations, KVM values, and product definitions to the runtime cluster. If the synchroniser loses connectivity, the runtime continues serving traffic with the last-known configuration.
More Related questions...