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.
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.
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].
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?
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.
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?
19 comments
[ 3.3 ms ] story [ 55.9 ms ] threadIt 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.
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...
I was always wondering if there was a "Cloudflare for APIs", i guess like what Mashery sort of was.
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.
[1] https://github.com/mybuilder/kongfig
- https://github.com/PGBI/kong-dashboard
- https://github.com/rsdevigo/jungle
- https://github.com/ajaysreedhar/kongdash
- https://github.com/lestoni/dashy