Mantenha tudo organizado com as coleções
Salve e categorize o conteúdo com base nas suas preferências.
O ambiente padrão do App Engine tem como base instâncias de contêiner em execução na infraestrutura do Google. Os contêineres são pré-configurados com um dos diversos ambientes de execução disponíveis.
Com o ambiente padrão, fica mais fácil criar e implantar um
aplicativo que será executado de maneira confiável, sob grande carga e com grandes quantidades de
dados.
Os aplicativos são executados em um ambiente seguro e colocado no sandbox, permitindo que o
ambiente padrão distribua solicitações em vários
servidores e escalone servidores para atender às demandas de tráfego. O aplicativo é executado em seu próprio ambiente seguro e confiável, independentemente do hardware, sistema operacional ou localização física do servidor.
Ambientes de execução e linguagens do ambiente padrão
O ambiente padrão é compatível com as seguintes linguagens:
A classe de instância determina o volume de memória e CPU disponíveis para cada instância, a cota gratuita e o custo por hora depois que o app excede a cota gratuita.
Para todas as gerações do ambiente de execução, o limite de memória inclui a memória que seu app usa com a memória que o próprio ambiente de execução precisa para executar seu app. Os ambientes de execução do Java usam mais memória para executar o app do que outros.
O ambiente padrão oferece 1 GiB de
armazenamento de dados e tráfego gratuitos, que podem ser aumentados com a ativação de aplicativos
pagos. No entanto, alguns recursos impõem limites não relacionados às cotas para proteger a estabilidade do sistema. Para mais detalhes sobre cotas, incluindo como editá-las para atender às suas necessidades, consulte Cotas.
Faça um teste
Se você começou a usar o Google Cloud agora, crie uma conta para avaliar
o desempenho do App Engine em situações
reais. Clientes novos também recebem US$ 300 em créditos para executar, testar e
implantar cargas de trabalho.
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Informações incorretas ou exemplo de código","incorrectInformationOrSampleCode","thumb-down"],["Não contém as informações/amostras de que eu preciso","missingTheInformationSamplesINeed","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 2025-04-09 UTC."],[[["\u003cp\u003eThe App Engine standard environment utilizes container instances on Google's infrastructure, preconfigured with various runtimes to support application deployment.\u003c/p\u003e\n"],["\u003cp\u003eThis environment ensures reliable application performance even under heavy loads and with large data volumes by using a secure, sandboxed system that distributes requests and scales servers automatically.\u003c/p\u003e\n"],["\u003cp\u003eThe standard environment supports a range of languages, including Go, Java, Node.js, PHP, Python, and Ruby, to accommodate different development preferences.\u003c/p\u003e\n"],["\u003cp\u003eInstance classes, such as F1, F2, B1, and B2, dictate the memory and CPU resources available to each instance, directly impacting the application's performance and operational costs.\u003c/p\u003e\n"],["\u003cp\u003eWhile the standard environment offers a free quota of data storage and traffic, it also incorporates certain system limits to maintain its stability and ensure optimal functionality.\u003c/p\u003e\n"]]],[],null,["# App Engine standard environment\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\nThe App Engine standard environment is based on container instances\nrunning on Google's infrastructure. Containers are preconfigured with one of\nseveral available runtimes.\n\nThe standard environment makes it easy to build and deploy an\napplication that runs reliably even under heavy load and with large amounts of\ndata.\n\nApplications run in a secure, sandboxed environment, allowing the\nstandard environment to distribute requests across multiple\nservers and scale servers to meet traffic demands. Your application runs\nwithin its own secure, reliable environment that is independent of the hardware,\noperating system, or physical location of the server.\n\nStandard environment languages and runtimes\n-------------------------------------------\n\nThe standard environment supports the following languages: \n[Go](/appengine/docs/standard/go/runtime) \n[Java](/appengine/docs/standard/java-gen2/runtime) \n[Node.js](/appengine/docs/standard/nodejs/runtime) \n[PHP](/appengine/docs/standard/php-gen2/runtime) \n[Python](/appengine/docs/standard/python3/runtime) \n[Ruby](/appengine/docs/standard/ruby/runtime)\n\nInstance classes\n----------------\n\nThe *instance class* determines the amount of memory and CPU available to each\ninstance, the amount of [free quota](/appengine/docs/standard/quotas#Instances), and the\n[cost per hour](/appengine/pricing#standard_instance_pricing) after your app\nexceeds the free quota.\n\nFor all runtime generations, the memory limit includes the memory your app uses\nalong with the memory that the runtime itself needs to run your app. The Java\nruntimes use more memory to run your app than other runtimes.\n\nTo override the default instance class, use the [`instance_class`\nsetting](/appengine/docs/standard/python3/config/appref#instance_class) in your\napp's `app.yaml` file.\n\nThe CPU values and limits reported in the instance class table don't reflect a\nfixed clock speed in the CPU. Instead, they represent the instance's\nallocated relative compute power or performance tier on the\n[shared-core](/compute/docs/general-purpose-machines#n1-shared-core) instance\ntype.\n\nSystem tools might report the total physical memory of the underlying host\nmachine. This is different from the instance's enforced memory limit, which is\nthe maximum memory available to the instance's isolated sandbox environment.\nExceeding this \"Memory Limit\", not the host's total RAM, might cause\nperformance issues.\n| **Important:** When you [view your bill](/billing/docs/how-to/reports), you will not see the names of the individual instance classes in your billing line items. Instead, you see instance hours from the \"B\" classes reported as \"Backend Instances\", and instance hours from the \"F\" classes reported as \"Frontend Instances\". The bill will apply the appropriate multiple of instance hours for each instance class you use. For example, if you use an F4 instance for one hour, you see \"Frontend Instance\" billing for four instance hours at the F1 rate.\n\nQuotas and limits\n-----------------\n\nThe standard environment gives you 1 GiB of\ndata storage and traffic for free, which can be increased by enabling paid\napplications. However, some features impose limits unrelated to quotas to\nprotect the stability of the system. For more details on quotas, including how\nyou can edit them to suit your needs, see [Quotas](/appengine/docs/standard/quotas).\n\nTry it for yourself\n-------------------\n\n\nIf you're new to Google Cloud, create an account to evaluate how\nApp Engine performs in real-world\nscenarios. New customers also get $300 in free credits to run, test, and\ndeploy workloads.\n[Try App Engine free](https://console.cloud.google.com/freetrial)"]]