Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update main_components.md #2821

Open
wants to merge 1 commit into
base: v2.4.x
Choose a base branch
from
Open

Update main_components.md #2821

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 8 additions & 8 deletions site/en/reference/architecture/main_components.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,28 +1,28 @@
---
id: main_components.md
summary: Learn about the main components in Milvus standalone and cluster.
summary: Learn about the main components in Milvus Standalone and Cluster.
title: Main Components
---

# Main Components

There are two modes for running Milvus: Standalone and Cluster. These two modes share the same features. You can choose a mode that best fits your dataset size, traffic data, and more. For now, Milvus standalone cannot be upgraded "online" to Milvus cluster.
There are two modes for running Milvus: Standalone and Cluster. These two modes share the same features. You can choose a mode that best fits your dataset size, traffic data, and more. For now, Milvus Standalone cannot be upgraded "online" to Milvus Cluster.

## Milvus standalone
## Milvus Standalone

Milvus standalone includes three components:
Milvus Standalone includes three components:

- **Milvus:** The core functional component.

- **Meta Store:** The metadata engine, which accesses and stores metadata of Milvus' internal components, including proxies, index nodes, and more.

- **Object Storage:** The storage engine, which is responsible for data persistence for Milvus.

![Standalone_architecture](../../../../assets/standalone_architecture.jpg "Milvus standalone architecture.")
![Standalone_architecture](../../../../assets/standalone_architecture.jpg "Milvus Standalone architecture.")

## Milvus cluster
## Milvus Cluster

**Milvus cluster** includes seven microservice components and three third-party dependencies. All microservices can be deployed on Kubernetes, independently from each other.
**Milvus Cluster** includes seven microservice components and three third-party dependencies. All microservices can be deployed on Kubernetes, independently from each other.

### Microservice components

Expand All @@ -40,7 +40,7 @@ There are two modes for running Milvus: Standalone and Cluster. These two modes
- **Object Storage:** Responsible for data persistence of large files in the cluster, such as index and binary log files, e.g. S3
- **Log Broker:** Manages logs of recent mutation operations, outputs streaming log, and provides log publish-subscribe services, e.g. Pulsar.

![Distributed_architecture](../../../../assets/distributed_architecture.jpg "Milvus cluster architecture.")
![Distributed_architecture](../../../../assets/distributed_architecture.jpg "Milvus Cluster architecture.")

## What's next

Expand Down