1e41f4b71Sopenharmony_ci# Process Model (FA Model)
2e41f4b71Sopenharmony_ci
3e41f4b71Sopenharmony_ci
4e41f4b71Sopenharmony_ciThe process model is shown below.
5e41f4b71Sopenharmony_ci
6e41f4b71Sopenharmony_ci
7e41f4b71Sopenharmony_ci- All PageAbility, ServiceAbility, DataAbility, and FormAbility components of an application (with the same bundle name) run in the same process, which is **Main process** in green in the figure.
8e41f4b71Sopenharmony_ci
9e41f4b71Sopenharmony_ci- WebView has an independent render process, which is **Render process** in yellow in the figure.
10e41f4b71Sopenharmony_ci
11e41f4b71Sopenharmony_ci**Figure 1** Process model
12e41f4b71Sopenharmony_ci
13e41f4b71Sopenharmony_ci![process-model-fa](figures/process-model-fa.png)
14e41f4b71Sopenharmony_ci
15e41f4b71Sopenharmony_ci
16e41f4b71Sopenharmony_ciThe system provides the following inter-process communication (IPC) mechanism:
17e41f4b71Sopenharmony_ci
18e41f4b71Sopenharmony_ciCommon events: This mechanism is used in one-to-many communication scenarios. Multiple subscribers may receive events at the same time.
19