Converting Backends to Services

Python 2.7/3.7 |Java 8/11 |PHP |Ruby |Go 1.9/1.11/1.12 |Node.js

Note: Services were previously called "modules".

The Backend API is deprecated as of March 13, 2014 and will be shut down on March 13, 2019. Developers are required to migrate all backend instances to Services, otherwise the instances will no longer be managable, and will stop serving traffic.

The original App Engine architecture is based on a single frontend instance with optional backend instances. If you have an application that uses backends, you might want to convert the backends to a service format to take full advantage of the additional functionality that services provide, such as the ability to version backends.

App Engine automatically runs an existing backend as a new, non-default version of the default service. Resident backends are assigned manual scaling and dynamic backends are assigned basic scaling.

You can convert backend instances to named services that are versioned and have explicit scaling type and instance classes. You must replace the original backends.xml file with multiple WAR files, one for each service. The procedure is as follows:

1. Create a top level EAR directory.
2. Create a META-INF subdirectory in the EAR directory that contains an appengine-application.xml file and an application.xml file.
3. Add service declaration elements to the application.xml file.
4. Create a subdirectory in the EAR directory for each service in the app including the default service. By convention, each subdirectory has the same name as the service it defines.
5. Copy the contents of the original WAR directory into each subdirectory. The original WAR should have a subdirectory named WEB-INF. Each new subdirectory must have its own copy of that directory.
6. Add service configuration elements to the appengine-web.xml files in each subdirectory to settings like service name, scaling, or instance class.
7. Application configuration files, such as cron.xml, dispatch.xml, or dos.xml, should only be included in the default service subdirectory. Remove these files from all the other service subdirectories.

For example, here is a file example/backends.xml that defines three backends (memdb, worker, and cmdline):

<backends>
 <backend name="memdb">
   <class>B8</class>
   <instances>5</instances>
 </backend>
 <backend name="worker">
   <options>
     <fail-fast>true</fail-fast>
   </options>
 </backend>
 <backend name="cmdline">
   <options>
     <dynamic>true</dynamic>
   </options>
 </backend>
</backends>

To convert these backends to services, first assume you've created a new EAR directory called "ear." Declare the backends as services in the file ear/META- INF/application.xml. Notice that this file also declares the default service as well:

<?xml version="1.0" encoding="UTF-8"?>
<application
  xmlns="http://java.sun.com/xml/ns/javaee"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
                      http://java.sun.com/xml/ns/javaee/application_5.xsd"
  version="5">

  <description>Demo Application</description>
  <display-name>My Java App</display-name>

  <!-- Default Module -->
  <module>
    <web>
      <web-uri>default</web-uri>
      <context-root>defaultcontextroot</context-root>
    </web>
  </module>
  <!-- Other Modules -->
  <module>
    <web>
      <web-uri>memdb</web-uri>
      <context-root>memdb</context-root>
    </web>
  </module>
  <module>
    <web>
      <web-uri>worker</web-uri>
      <context-root>worker</context-root>
    </web>
  </module>
  <module>
    <web>
      <web-uri>cmdline</web-uri>
      <context-root>cmdline</context-root>
    </web>
  </module>
</application>

The configuration for each service is written in a separate appengine-web.xml file, under the corresponding subdirectory. In ear/memdb/WEB-INF/appengine-web.xml:

<appengine-web-app xmlns="http://appengine.google.com/ns/1.0">
  <application>my-java-app</application>
  <module>memdb</module>
  <version>uno</version>
  <threadsafe>true</true>
  <instance-class>F4</instance-class>
  <manual-scaling>
    <instances>5</instances>
  </manual-scaling>
</appengine-web-app>

In ear/worker/WEB-INF/appengine-web.xml:

<appengine-web-app xmlns="http://appengine.google.com/ns/1.0">
  <application>my-java-app</application>
  <module>worker</module>
  <version>uno</version>
  <threadsafe>true</threadsafe>
   <!-- For failfast functionality, please use the ‘X-AppEngine-FailFast’ header on requests made to this module. -->
  <instance-class>F2</instance-class>
  <manual-scaling>
    <instances>5</instances>
  </manual-scaling>
</appengine-web-app>

In ear/cmdline/WEB-INF/appengine-web.xml:

<appengine-web-app xmlns="http://appengine.google.com/ns/1.0">
  <application>my-java-app</application>
  <module>cmdline</module>
  <version>uno</version>
  <threadsafe>true</threadsafe>
  <instance-class>F2</instance-class>
  <basic-scaling>
    <max-instances>10</max-instances>
  </basic-scaling>
</appengine-web-app>

Tip: For details and additional examples of the App Engine configuration files, see the Configuration Files Overview.