API Gateway for Google Cloud Functions?

Question

Google Cloud Platform

There is a "Cloud Endpoints" service, but all the tutorials and docs look very unclear.

First, there is a cost per number of requests to the Cloud Endpoint.

Secondly, the official guide suggests deploying a Cloud-run instance , I believe for an additional fee. What's wrong with it? The serverless architecture is supposed to make my life easier. Why on earth should I deploy a Cloudrun container to get Cloud-endpoints working to make Cloud Functions a production-ready architecture?

Also, there are no proper docs on how to handle all these services during local development. On github functions-frameworkis it suggested to create another function that will bundle other functions because functions-framework can't properly handle multiple functions at the same time? Seriously damn? It all looks like I'm going in the wrong direction.

I have the usual needs to write and read data from MongoDB, process payments with Stripe, and so on. Why does it feel like I'm writing a php server in 2010?

So what am I supposed to use as the API Gateway for Google Cloud Functions? And what about local development of a backend consisting of several functions?

Thank you!

Answer 1

Well, first of all, trying to get into serverless via GCP is a very bad idea. They didn’t adequately do anything except firebase in this direction, alas.
Perhaps a completely unknown and useless framework will help :-)
And secondly, as for requests, welcome here - in serverless, the payment system occurs as requests and traffic (+ Storage for databases)