Cloud Endpoints is a distributed API management system. It provides an API console, hosting, logging, monitoring and other features to help you create, share, maintain, and secure your APIs. This page provides an overview of Cloud Endpoints for gRPC. For information on other types of API frameworks supported by Cloud Endpoints, see All Endpoints Docs.
Cloud Endpoints uses the distributed Extensible Service Proxy (ESP) to provide low latency and high performance for serving even the most demanding APIs. The Extensible Service Proxy is a service proxy based on NGINX, so you can be confident that it scales as needed to handle simultaneous requests to your API. The proxy runs in its own Docker container for better isolation and scalability and is distributed in the Google Container Registry and Docker registry. It can be used with Google App Engine flexible, Google Kubernetes Engine, Google Compute Engine or Kubernetes.
Cloud Endpoints uses Google Service Management for managing APIs and Google Service Control for reporting logs and metrics. You can manage and monitor your APIs using the Endpoints dashboard in the Google Cloud Platform Console.
Hosting an API
Cloud Endpoints is optimized for the Docker container environment. You can host your API anywhere Docker is supported so long as it has Internet access to Google Cloud Platform.
However, Cloud Endpoints provides an optimized workflow to run your APIs on the following:
- Compute Engine
- Kubernetes Engine
- App Engine flexible environment, which includes built-in Extensible Server Proxy.
Developing a gRPC API with Cloud Endpoints
Write your gRPC API service configuration for Endpoints.
Generate the runtime API configuration for your API and deploy it to Google Service Management.
Deploy your API server.
Controlling API access
Cloud Endpoints lets you configure your API to require an API key for any call and validates the API key. You can also use the Google Cloud Platform Console to share your API with other developers so they can enable your API and generate API key(s) to call it.
Authenticating API users
Note that your API server still needs to decide what the authenticated user can do with your API. For more information, see the Google Cloud Platform Auth Guide.