cloud-run-faq

> there is no easy way to manage secrets with Cloud Run See https://cloud.google.com/secret-manager/ I recommend this community-maintained FAQ on Cloud Run: https://github.com/ahmetb/cloud-run-faq

I did this kind of research in the last two weeks. I have got a huge spreadsheets with goals and various options how to fulfil these goals with the cloud offerings of just aws and gcp. So the fun part here is, several options are viable, until you find this one issue where it doesn't work anymore. then you have to track back or find work around and check if the work arounds are acceptable or not. And some of these limitations are usually not that straight forward to see and also to read about. However, there are some resources like https://github.com/ahmetb/cloud-run-faq which are very good and helpful. Sometime official documentation doesn't really cover the questions that are important for your product. Also, what i found without a multiples poc testing connectivity and the basic building blocks it is difficult to find all the gotchas,

From: https://github.com/ahmetb/cloud-run-faq#how-to-keep-a-cloud-... --- How to keep a Cloud Run service “warm”? You can work around "cold starts" by periodically making requests to your Cloud Run service which can help prevent the container instances from scaling to zero. Use Google Cloud Scheduler to make requests every few minutes. Does my application get multiple requests concurrently? Contrary to most serverless products, Cloud Run is able to send multiple requests to be handled simultaneously to your container instances. Each container instance on Cloud Run is (currently) allowed to handle up to 80 concurrent requests. This is also the default value. What if my application can’t handle concurrent requests? If your application cannot handle this number, you can configure this number while deploying your service in gcloud or Cloud Co