> The service will create more and more instances of your application up to the limit you defined (currently the cap is 1000 instances). > As long as you have

> The service will create more and more instances of your application up to the limit you defined (currently the cap is 1000 instances). > As long as you have architected your application to be stateless - storing data in something like a database (eg CloudSQL) or object storage (eg Cloud Storage) - then you are good to go. Won’t this just defer the scalability issue to the SQL part of the application? It’s nice that the stateless REST part can be scaled almost infinitely, but if the SQL part doesn’t offer the same scalability, what’s the point? Last time I looked, CloudSQL didn’t offer this kind of scalability.