Getting Stuck with Apigee: Anyone Else Struggling with Vendor Lock-in?
Asked by
TechieTurtle92
I need some advice! We deployed Apigee under the impression it was cloud-agnostic based on what the sales rep told us, but now we've discovered that it functions best on Google Cloud Platform (GCP). While it can technically run elsewhere, it loses key features and performance suffers tremendously. We're primarily using AWS for our infrastructure, with some Azure for compliance needs, but now our API gateway is in GCP, causing our latency to shoot up from 50ms to 180ms. Plus, we can't even use CloudWatch for monitoring since it's split between GCP and AWS. The contract is up in four months, and management is questioning the decision to lock ourselves into a cloud we hardly utilize. We're considering alternatives, but it seems like AWS API Gateway only supports AWS, and Azure's APIM only works on Azure. I've heard about Kong and Tyk being cloud-agnostic, but I'm unsure if they would work for us. Has anyone successfully migrated away from a vendor-locked gateway?
Answers
Definitely don't trust everything sales tells you! Always do your own research and consider consulting an engineer before signing contracts. It's a good practice to avoid future headaches.
Reply to this answer
I work for HAProxy Technologies, and we offer a solution called Fusion Control Plane, which provides solid API Gateway capabilities across various Kubernetes clusters and other resources. You can even create a custom solution with our Dataplane API project if you want flexibility!
Reply to this answer
I've had a similar experience with Azure's API Management. We were stuck with Azure too, even though we wanted to move everything to AWS to cut costs. Vendor lock is a real trap! Eventually, we switched to Gravitee, which is cloud-agnostic and can run on AWS, Azure, or Kubernetes. The migration took about six weeks which wasn’t too bad compared to being locked in for another year. The hardest part was getting the management on board after the whole mess with Azure.
Reply to this answer
Have you looked into Apigee Hybrid? It can actually be deployed on AWS and Azure while still having management on GCP. This way, you might avoid some of the latency issues.
Reply to this answer
The downside of 'cloud-agnostic' is that you often sacrifice native integrations. Apigee works seamlessly with GCP, but if you want to use something like Kong, be prepared to do some of the building yourself.
Reply to this answer
Add your answer
Answers are reviewed before publication.
Related Discussions