Back to Details

qdrant-deployment-options

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Which Qdrant Deployment Do I Need?

我需要哪种Qdrant部署方案？

Start with what you need: managed ops or full control? Network latency acceptable or not? Production or prototyping? The answer narrows to one of four options.
先从你的需求出发：需要托管运维还是完全控制权？网络延迟是否可接受？是生产环境还是原型开发？根据这些问题的答案可以将可选范围缩小到四个方案之一。

Getting Started or Prototyping

入门或原型开发

Use when: building a prototype, running tests, CI/CD pipelines, or learning Qdrant.
  • Use local mode (Python only): zero-dependency, in-memory or disk-persisted, no server needed Local mode
  • Local mode data format is NOT compatible with server. Do not use for production or benchmarking.
  • For a real server locally, use Docker Quick start
适用场景：构建原型、运行测试、CI/CD流水线，或者学习Qdrant。
  • 使用本地模式（仅支持Python）：零依赖，支持内存存储或磁盘持久化，无需启动服务 本地模式
  • 本地模式的数据格式与服务端不兼容，请勿用于生产环境或性能基准测试。
  • 如需在本地运行完整的Qdrant服务，可使用Docker 快速入门

Going to Production (Self-Hosted)

生产环境部署（自托管）

Use when: you need full control over infrastructure, data residency, or custom configuration.
  • Docker is the default deployment. Full Qdrant Open Source feature set, minimal setup. Quick start
  • You own operations: upgrades, backups, scaling, monitoring
  • Must set up distributed mode manually for multi-node clusters Distributed deployment
  • Consider Hybrid Cloud if you want Qdrant Cloud management on your infrastructure Hybrid Cloud
适用场景：你需要对基础设施、数据驻留或自定义配置拥有完全控制权。
  • Docker是默认部署方式，支持Qdrant开源版全部功能，部署成本极低 快速入门
  • 你需要自行负责运维工作：升级、备份、扩容、监控
  • 如需多节点集群，必须手动配置分布式模式 分布式部署
  • 如果你希望在自有基础设施上使用Qdrant Cloud的托管能力，可以考虑Hybrid Cloud方案 Hybrid Cloud

Going to Production (Zero-Ops)

生产环境部署（零运维）

Use when: you want managed infrastructure with zero-downtime updates, automatic backups, and resharding without operating clusters yourself.
  • Qdrant Cloud handles upgrades, scaling, backups, and monitoring Qdrant Cloud
  • Supports multi-version upgrades automatically
  • Provides features not available in self-hosted: 
    /sys_metrics
    , managed resharding, pre-configured alerts
适用场景：你希望使用托管基础设施，无需自行运维集群即可享受零停机更新、自动备份和重分片能力。
  • Qdrant Cloud负责处理升级、扩容、备份和监控 Qdrant Cloud
  • 自动支持多版本升级
  • 提供自托管版本不具备的功能：
    /sys_metrics
    、托管重分片、预配置告警

Need Lowest Possible Latency

需要最低延迟的场景

Use when: network round-trip to a server is unacceptable. Edge devices, in-process search, or latency-critical applications.
  • Qdrant EDGE: in-process bindings to Qdrant shard-level functions, no network overhead Qdrant EDGE
  • Same data format as server. Can sync with server via shard snapshots.
  • Single-node feature set only. No distributed mode.
适用场景：无法接受访问服务端的网络往返耗时，比如边缘设备、进程内搜索，或者对延迟要求极高的应用。
  • Qdrant EDGE：进程内绑定Qdrant分片级功能，无网络开销 Qdrant EDGE
  • 与服务端使用相同的数据格式，可通过分片快照与服务端同步数据
  • 仅支持单节点功能，无分布式模式。

What NOT to Do

注意事项

  • Use local mode for production or benchmarking (not optimized, incompatible data format)
  • Self-host without monitoring and backup strategy (you will lose data or miss outages)
  • Choose EDGE when you need distributed search (single-node only)
  • Pick Hybrid Cloud unless you have data residency requirements (unnecessary Kubernetes complexity when Qdrant Cloud works)
  • 不要在生产环境或基准测试中使用本地模式（未做性能优化，数据格式不兼容）
  • 自托管时不要缺少监控和备份策略（否则可能丢失数据或者无法及时感知故障）
  • 需要分布式搜索时不要选择EDGE（仅支持单节点）
  • 除非有数据驻留要求，否则不要选择Hybrid Cloud（Qdrant Cloud可满足需求时无需额外承担Kubernetes复杂度）