Deploying-kubernetes-apis-at-scale-with-Apigee-Pattern with Apigee Hybrid instead of Apigee Microgateway

[abiramradhakris]

As per the Deploying-kubernetes-apis-at-scale-with-Apigee indicates

Q1: Have following queries based Pattern 2 and Pattern 3? Can we perform the same with with Apigee Hybrid instead of Apigee Microgateway ?

Q2. Looks like Pattern 1 and Pattern 2 and Pattern 3 can work on GCP/Azure/AWS Cloud but will this work with AKS (Azure Kubernetes Service) and Amazon EKS instead of GKE with Apigee SaaS ?

Q3: If Q2 is sully possible or possible with say AKS (Azure Kubernetes Service) only does the Strength and limitations indicated remains same ?

[basavarajdhanas]

#1: Microgateway is a solution offered to mainly address cross-cutting concerns for east-west communication. Its a subset of full-fledge gateway solution provided. It has to sit next to your microservices/downstream APIs.

Apigee Hybrid is itself another improved (containerized) version of API gateway solution provided to the existing on-prem or saas Apigee API gateway (which is mainly installed on VMs).

Apigee Hybrid can be deployed in the same Kubernetes cluster where your microservices are deployed in Kubernetes. Of course, you have to separate all deployments in different namespaces. If you have an Apigee Hybrid solution, I don't think you need a micro gateway solution anymore. It's addressing both east-west and north-south traffic concerns.

#2: All these patterns should work on any Kubernetes services.

#3: Yes, they can remain same irrespective of Kubernetes vendor, after all, the micro gateway is deployed as just another POD/service on Kubernetes.

[abiram8]

Thanks @Basavaraj Dhanshetti for response

[dchiesa1]

It would be nice if the "microgateway" pattern could be implemented with different gateways. Like Envoy for example.