Apigee Edge Vs Google Cloud Endpoints - Which one to use when ?

Let's say, A company X hosted services on Google Cloud & They are really interested to do API Management for the services hosted on Google Cloud Platform. Since, Apigee is now part of Google ,

  • Should they be using Apigee Edge instead of Google Cloud Endpoints ?
  • Should they use both of them ? Let's say Google Cloud Endpoints like an API Gateway to do API Traffic Management / Mediation & Apigee for Analytics & Developer Services ?
  • Is there a reference architecture that would suggest use best of both ?
  • How does Google Cloud Endpoints fit in Apigee / API Management story ?
Solved Solved
6 2 24.1K
1 ACCEPTED SOLUTION

Both Apigee and Cloud Endpoints are built with a goal to manage all your APIs.

Endpoints is API management gateway which helps you develop, deploy, and manage APIs on any Google Cloud backend. It runs on GCP and leverages a lot of Google's underlying infrastructure. It also has native hooks to integrate with other products in GCP suite. If you have applications running on GCP, then Endpoints can enable you quick build APIs around them.

Apigee on the other hand is a comprehensive API management platform built for Enterprises, with deployment options on cloud, on-premises or hybrid. The feature set includes a full-fledged API gateway, customizable portal for on-boarding partners and developers, monetization, and deep analytics around your APIs. It also out of the box configurations to support traffic management, mediation, security, packaging APIs, developer key management etc. You can use Apigee for any http/https backend, no matter where they are running (on-premises, any public cloud etc.).

If you are using GCP, then there are use-cases for you to use both in your architecture. But if you have not GCP backend, you only use Apigee.

View solution in original post

2 REPLIES 2

Both Apigee and Cloud Endpoints are built with a goal to manage all your APIs.

Endpoints is API management gateway which helps you develop, deploy, and manage APIs on any Google Cloud backend. It runs on GCP and leverages a lot of Google's underlying infrastructure. It also has native hooks to integrate with other products in GCP suite. If you have applications running on GCP, then Endpoints can enable you quick build APIs around them.

Apigee on the other hand is a comprehensive API management platform built for Enterprises, with deployment options on cloud, on-premises or hybrid. The feature set includes a full-fledged API gateway, customizable portal for on-boarding partners and developers, monetization, and deep analytics around your APIs. It also out of the box configurations to support traffic management, mediation, security, packaging APIs, developer key management etc. You can use Apigee for any http/https backend, no matter where they are running (on-premises, any public cloud etc.).

If you are using GCP, then there are use-cases for you to use both in your architecture. But if you have not GCP backend, you only use Apigee.

Hi folks, is Apigee an substitute for GCP in the future? Which one would be better for start a project from the scratch? Thanks for all the explanations!