Manage your APIs with Google Cloud Endpoints | Hacker News Reader

Manage your APIs with Google Cloud Endpoints

cloudplatform.googleblog.com

62 pointsrey12rey18 comments

Seems similar to Mashape Kong - really happy with Kong - https://github.com/Mashape/kong

Kong has been working without problems in our (small-scale) setup since we introduced it a few months back. Personally not too fond of the tooling to configure apis and consumers/credentials though. Is there a better way to manage these things than with curl?

I've used Kongfig [1] for use with automated provisioning.

[1] https://github.com/mybuilder/kongfig

There are several open-source admin/dashboards GUI built by the community. Here a few:

- https://github.com/PGBI/kong-dashboard

- https://github.com/rsdevigo/jungle

- https://github.com/ajaysreedhar/kongdash

- https://github.com/lestoni/dashy

The whole thing is quite confusing. Is this open source? Is there any demo app that shows how it all works(i.e. the Service Control)? Last time I've checked 'cloud endpoints' was a half baked solution on appengine. I didn't have a good experience with swagger either.

There are some nice examples here: https://cloud.google.com/endpoints/docs/frameworks/python/cr...

It seems like an interesting and useful approach, and it can optionally handle some of the OAuth2 stuff for you when clientIds managed by google. I've been staying away from GCP, but now kind of interested how this works.

Hi -- PM on the product here.

Both of our API frameworks have been open sourced (Java[0], Python[1]). Those used to be available only on App Engine Standard Environment but can now be used anywhere. This was a top request of people using Flexible Environments.

But we've added a bunch of functionality to the platform (logging, monitoring, user authentication, tracing) that people can use whether or not they're using our frameworks -- for example, Python+Flask, NodeJS + Express, etc. To use it, you set it up with an OpenAPI Specification (FKA Swagger Spec). We've seen tons of interest in OpenAPI and even joined the Open API Initiative to foster that community.

If you are interested in a walkthrough (that uses Python and Flask), see [2].

[0]https://github.com/cloudendpoints/endpoints-management-java [1]https://github.com/cloudendpoints/endpoints-management-pytho... [2]https://cloud.google.com/endpoints/docs/quickstart-app-engin...

Can you provide keys to API clients and limit the keys to X requests per month?

You can require API keys and provide them to clients. We'll be adding rate limits and quotas soon as well. Are you more interested in X per month or X per second?

Interested in both. But more interested in X per month for SaaS billing, etc.

Any idea when the rate limits and quotas will be available? Trying to decide whether to use GC or AWS

for the proxy are you using NGINX with Lua?

It's pure C++ for now for performance reasons.

IMO NGINX/Openresty is on par with native C++ in terms of performances, but more maintainable long term.

I think this is basically a competitor to AWS API Gateway: https://aws.amazon.com/api-gateway/

So do you have to run on Google Cloud or can it work as a proxy Cloudflare-style?

I was always wondering if there was a "Cloudflare for APIs", i guess like what Mashery sort of was.

It runs everywhere. Here's an example of it running in a kubernetes cluster, regardless of where it's hosted: https://github.com/GoogleCloudPlatform/endpoints-samples/tre...

It's the "-k" parameter (key file) that lets you run it outside of Google Cloud. Credentials are automatically provided when you run it inside Google Cloud.

The proxy is packaged as a docker image, it can run anywhere docker is supported. For performance and convenience, the proxy and the server typically run next to each other, but that is not required.

Reply on news.ycombinator.com