Hi Richard, instances are not shared across services, each service has its own instances (you can define different scaling and instances classes per service).
In your billing, you will not see the instance hours broken down to services, but for all services of the project together. This also means that if you have low traffic per service you may see under-utilization of instances, compared to a monolithic app with just one service. Hope that clarified it a little. Ani On Monday, August 20, 2018 at 2:30:24 PM UTC+2, Richard Cheesmar wrote: > > > Regarding App Engine Microservice costs, in the Google docs, it states the > following > > Costs for instance-hours (the CPU and memory for running your code) are > not separated for services; all the instance-hours for an entire project > are lumped together. > > Can anyone tell me if this implies that for example there is n instances > on a project that are shared across all microservices or does each > microservice have a separate instance that is charged at a base rate and > then on top instance hours used. > > Thanks > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/bfc7b3b8-70e7-4621-9812-ca85ed82f67e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
