Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Cloud run looks cool, but doesn't seem to support databases ? Unless it supports linked containers?

I like that it's a mix of AWS lambda scaling with more open environments... Though it's hard to read through the marketing... "Nearly instance availing from 1 to 1000"



Cloud Run user here. It does not support running a database as a Cloud Run service; you'd need to connect to a Cloud SQL instance. This is one area I really hope PaaS providers improve on in the future. The closest thing at the moment is Aurora Serverless on AWS, especially with their neat HTTP connection system. That being said, cold starts are even worse since they're now the start up time for your application in addition to the start up time for Aurora Serverless.


But, correct me if this has changed please, last i checked Cloud Run did not support private networks. So you SQL instance has to be exposed to the internet, correct?


Your Cloud SQL instance would have a public IP, but would not be exposed to the internet. All traffic is blocked by default. Only GCP service accounts with the right permissions can make connections to your SQL instance, or IPs added to a whitelist (not recommended).


Ah, thanks for clearing that up, I was unaware. How is the traffic blocked by default? Firewall layer?


Yes. There is a proxy in front of the database which only allows whitelisted traffic (dangerous) or traffic with a valid cert (safe).


Yes, Cloud Run requires your Cloud SQL instance to have a public IP address.


You might want to check out FaunaDB.


Unfortunately FaunaDB isn't a SQL database, so it's in the same class as things like Cloud Firestore, AWS DynamoDB, and Mongo Atlas. Good datastores for serverless applications, but not so great for traditional applications migrated to serverless.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: