iSulad/docs/architecture_en.md

# iSulad Architecture

## Overview

![architecture](design/arch.jpg)

iSulad is an OCI-compliant container runtime engine that emphasizes simplicity, robustness, performance and lightweight. 

As a daemon process, it manages the entire container life cycle of the host system, including image transmission and storage, container execution and monitoring management, container resource management, and network management. iSulad provides Docker-like CLI for users.

You can use Docker-like commands to manage container images and iSulad provides gRPC APIs which comply with the CRI standard for Kubernetes. 

iSulad is divided into different modules, and the modules are organized into subsystems. Understanding these modules, subsystems, and their relationships is important to modify and extend iSulad. 

This document describes the high-level system architecture design. For more information about each module, please refer to the relevant design documents. 

## Subsystem

You can interact with the iSulad by invoking gRPC APIs exported by the subsystem. 

- **image service** :   Image management service, provides image-related operations, such as image download, query, and deletion. 
- **execution service**:  Container life cycle management service, provides container-related operations, such as container creation, startup, and deletion. 
- **network**：The network subsystem is responsible for network management capabilities of the pod of the CRI. When a pod is started, the pod is added to the network plane specified in the configuration file through the CNI interface. When a pod is stopped, the CNI API is used to remove the pod from the network plane where the pod is located and clear related network resources. 

## Module 

- **image content** :   Managing Image Metadata and Container File Systems 

- **resource manage**:  Container resource management module, for example, setting available CPU and memory resource limits 

- **Executor**：Runtime for executing actual container operations. The LCR acts as the default runtime and can be extended through the plug-in mechanism. 

- **Events**：Container event collection module

- **Plugins**：Provides the plugin mechanism to extend container capabilities through different plugins.

- **HA**：This module provides fault locating and garbage collection service. 

### Network architecture design 

The figure shows the architecture:

![CNI_architecture](./design/CNI_architecture.png)