Google Cloud Launches its API Gateway in Beta
Google announced the beta of API Gateway—a fully-managed Google Cloud offering that let users create, secure, and monitor APIs for their serverless workloads.
The fully-managed API Gateway helps developer in managing API calls to serverless backends.
This new service is built on Envoy, giving Google cloud users performance and scalability with both consumption-based and tiered pricing options.
Envoy is an open source cloud-native high-performance edge/middle/service proxy. Originally built at Lyft, Envoy is a high performance C++ distributed proxy designed for single services and applications, as well as a communication bus and “universal data plane” designed for large microservice “service mesh” architectures.
The new API Gateway enables developers to easily bundle many services into APIs, while making them accessible through a single interface and simple for consumers .
API Gateway allows developers to provide safe access to their backend services through a well-defined REST API that is consistent across all of their services , regardless of the implementation of the service. Clients consume REST APIS to implement standalone apps for a mobile device or tablet, through apps running in a browser, or through any other type of app that can make a request to an HTTP endpoint.
Google's new Gateway API provides developers with three simple ways to communicate with the tools and services required to build APIs:
- Using the Google Cloud Console
- Using the gcloud command-line interface
- Or by integrating client libraries
The price for API Gateway depends on the number of calls to your API. According to Google, API Gateway charges by its calls to Service Control. Each API call processed by API Gateway is reported as a tracked operation by the Service Control API and is listed as a line item for Service Control on your bill.
|API calls per month per billing account||Cost per million API calls|
Ingress is always free, however general network usage applies to data that exits Google (Egress)
|Source and destination of traffic||0-10 TB||10 TB-150 TB||150 TB+|
|North America to North America||$0.105||$0.080||$0.060|
|Europe to Europe||$0.105||$0.080||$0.060|
|Asia Pacific to Asia Pacific||$0.120||$0.085||$0.080|
|South America to South America||$0.120||$0.085||$0.080|
|Oceania to Oceania||$0.120||$0.085||$0.080|
|Intercontinental (excluding Oceania and China)||$0.120||$0.085||$0.080|
|Intercontinental to/from Oceania||$0.190||$0.160||$0.150|
|Any traffic to China||$0.190||$0.160||$0.150|
We had challenges with scaling and consolidation of different API call types prior to implementing the API Gateway. Not only have we resolved issues, but we’ve experienced a 10x improvement in API management by using a single platform that is easily accessible through the cloud console and fully managed by Google Cloud.Fabian SeitzTechnical Product Manager at MediaMarktSaturn