Deployment Architecture for Apigee Hybrid API Management
Here in this blog, we will learn about the deployment architecture for Apigee hybrid API Management.
Apigee Hybrid is an API management platform that enables organizations to deploy API gateways in a hybrid environment. It combines the advantages of both on-premises and cloud deployments, allowing for centralized control while maintaining local processing and data sovereignty. With Apigee, you can manage, secure, and analyze APIs effectively, ensuring seamless integration with your existing infrastructure.
Key Components of Apigee Hybrid
-
Management Plane
The management plan is hosted in the Google Cloud Platform (GCP) and is responsible for:
API Lifecycle Management: Designing, deploying, and versioning APIs.
Developer Portal: Providing a platform for API documentation, testing, and onboarding.
Analytics: Monitoring and analyzing API usage, performance, and security.
Security: Implementing policies for authentication, authorization, and threat protection.
-
Runtime Plane
The runtime plane can be deployed in various environments, including on-premises data centers, Google Kubernetes Engine (GKE), or other cloud providers. It handles:
API Proxy Processing: Routing, transforming, and enforcing policies on API requests and responses.
Data Plane: Managing API traffic and ensuring high availability and performance.
-
Apigee Connect
Apigee Connect is a secure communication channel between the management plane and the runtime plane. It ensures that configuration changes, analytics data, and other management tasks are synchronized efficiently.
-
Kubernetes Cluster
Apigee Hybrid leverages Kubernetes for orchestrating the runtime components. The Kubernetes cluster provides:
Scalability: Automated scaling of API proxies based on traffic.
Resilience: High availability and fault tolerance for runtime components.
Management: Simplified deployment and management of containers.
Prerequisites for Apigee Hybrid Deployment
Before deploying Apigee Hybrid, ensure the following prerequisites are met:
- Google Cloud Project: A GCP project with billing enabled.
- Kubernetes Cluster: A Kubernetes cluster (GKE or on-premises) with sufficient resources.
- Service Accounts: GCP service accounts with necessary permissions for Apigee Hybrid.
- Networking: Proper network configuration to allow communication between the management and runtime planes.
