Why does all the documentation only show serverless options as backend services? Can you use other options (VMs, external webservers) as well? If yes, to what limit? Only endpoints that can be reached over Internet?

Are there any good resources on how to setup custom domains with API-gateway?

How is this different from Cloud Endpoints and Apigee?

@broli720

3 жыл бұрын

It's the same as Apigee. Apigee is more enterprise focused and is super expensive. API Gateway is for smaller scale deployments. Not sure about cloud endpoints though.

How do you manage the open api spec on environments with CI/CD in mind?. Knowing that every service is isolated from the others, looks complex or am i missing something?

@Pirake123

2 жыл бұрын

You need to create a new config each time (e.g v1, v2) and then get the API gateway to point at the new config. There are some gcloud commands for this. Its not ideal though as we can't just do an update command. So I would just setup a build trigger that builds a new config when its created and then add a buildstep that points the api gateway to the latest config.

@StanleySathler

3 ай бұрын

@@Pirake123 thanks for clarifying. Considering services aren't aware of each others, what people often do - on every CI build, generates a new OpenAPI spec from the code, then update the config? The project I work for uses Kong, so apparently they use Kong's Admin SDK to register the services without the need for an OpenAPI spec.

Awesome!!

API key is not working for me. It's invoking cloud function even without passing key.

does this support websocket like AWS API Gateway ?

@jeanbaro8498

2 жыл бұрын

No, it doesn't... There are a lot of basic features GCP has to add to this to be comparable to AWS's gateway, but they are moving well!

I already used this with my several Cloud Run. It's slow at first call.

@anandakumarsanthinathan4740

2 жыл бұрын

It is probably the way you have the Cloud Run services setup and nothing to do with the API Gateway itself. If you have at least one Cloud Run instance 'warm', then only the very first call may have some delay and not the rest of the calls. If all the instances are cold, then after the last invocation, the instances die and when a new call comes in, there is a delay in getting that instance ready to serve.

Is this something similar to Apigee?

@MakkaraKuski

3 жыл бұрын

yes,

@WilfredvanderDeijl

3 жыл бұрын

Makkara Kuski but much more affordable. Apigee costs serious $$$

how is it different from https load balancer? Or microservices would be running in kubernetes anyhow, why not use the ingress gateway or better yet, an Istio ingress gateway ?

@MakkaraKuski

3 жыл бұрын

cost: kubernetes engine costs ~100usd/month and then you pay for the machines. loadbalancer also costs $20/month plus the network transfer. cloud run + apigateway is almost free - you only pay for the isage. also because its and API gateway it has API key management and traffic limiting built-i

@anandakumarsanthinathan4740

2 жыл бұрын

The load balancer is to split the traffic across 'identical' services. But you can put any number of services, however different they are, behind an API Gateway. It is not so much for traffic splitting or load-balancing, rather for routing the incoming requests to the right service.

Where to use it and y

@WilfredvanderDeijl

3 жыл бұрын

It seems like it is not listed (yet) on the GCP product page, but documentation can be found at cloud.google.com/api-gateway/docs For now it looks very similar to the already existing Google Cloud Endpoints and I struggle to find the key differences

@CloudAdvocate

3 жыл бұрын

@@WilfredvanderDeijl Yes! If you are using one function. But let's say you have multiple functions with each different functionality..you can create one end point and access multiple functions as opposed to calling them individually. Also, hopefully they will have caching and canary deployments etc in future.

Enabling the "API Gateway API" will load forever and not succeed...

@grandfleet

3 жыл бұрын

I have the exact same problem

@BradleyWeston92

3 жыл бұрын

Try enabling using gcloud cli

@YogendraJ

3 жыл бұрын

It shows as loading forever, but if you refresh the page, the API is already enabled. Somehow the UI doesn't get refreshed by itself :)

@StanleySathler

3 ай бұрын

Takes some time in my case too (~2 minutes), but it succeeds at some point