Google - posting articles like the one referenced by steve174 above is a complete waste of time. It doesn’t answer anything. Clearly written by your marketing team intended for… who knows, but definitely not us engineers.
Some examples:
- “API adoption is exploding everywhere” - er, yeah, we know. Maybe get right to the point next time.
- “Apigee lets you operate in any environment of your choice (on-premises, in Google Cloud, or a hybrid environment) with enhanced scale, security and automation”. - cool. What exactly has been “enhanced”? Are you saying Api Gateway on the other hand is not as secure!? What about authorisation options, do either one support external authorisers? What about protocols (OAuth, SAML, etc); which ones does each service support? With scale, how much more exactly can Apigee scale compared to API Gateway? Ty this. Google “gcp api gateway maximum requests per second”. Not very useful list of results is it? Now try the same search but with the gcp bit removed. See the difference? Even AWS (the epitome of rubbish documentation) has done better here.
Oh there’s a lot more I can remark on but hopefully the message is clear. No, it’s not to respond to my 2 remarks above, it’s for you to go away and reflect. Next time, get your engineers to write the comparison article and put in actual pragmatic differences, and not a marketing dump - you’re not selling it and we’re not buying it.
Better yet, in the future, maybe go with a single service and add capabilities to it, leaving it to the consumer to pick and choose how simple or complex they wanna make it, as opposed to a bunch of completely separate services, each seemingly doing the same thing.
We’re in the process of shifting all our AWS infra to a new provider, and GCP is among the potential candidates. I won’t be holding this particular issue against you, but I can’t say the same for the next engineer.