"Erlang / OTP concurrent programming combat" Chapter X package, and deploy service

1. Application Controller:
   1. There is only one controller for each application is running, it registered the name application_controller.
   2. The controller responsible for loading the .app file applications, and checks to see if other applications currently dependent applications have been started.
   3. The application controller will derive one pair of master process applications running in each application, and thus their own application code to isolate.
   4. With application: When start (AppName) launch the application, start the application type of default is temporary.
   5. If by application: start (AppName, permanent) start, as long as the application is terminated, the entire operating system will be closed and re-start.
2. Published Mirror:
   1. Several applications, plus some metadata, constitute the release image.
   2. Metadata is used to describe how a systematic way to launch and manage these applications.
   3. The same publishing applications in the mirror are running on the system when running on the same set of Erlang, which is the target system.
   4. The version number is one of the important attributes of a publication mirror.
3. Publishing steps mirror:
   1. Determine which applications need to include
   2. Create a publication describing the contents of image metadata file (.rel)
   3. Creating a Startup Script
      1. .script .boot files and documents.
      2. Within .script file contains a complete specification, the contents of all the applications listed, including all the details, including the path of the application modules to load, and various other necessary information.
      3. .boot file is a binary form .script files available for ERTS read directly at startup.
      4.  
   4. Create the System Configuration File
   5. The contents of all packaged into a single file
4.