Help Center/ GaussDB/ FAQs/ About GaussDB/ What Are the Differences Between the Independent Deployment Model and Combined Deployment Model of GaussDB Distributed Instances?
Updated on 2024-11-11 GMT+08:00
View PDF
Share

What Are the Differences Between the Independent Deployment Model and Combined Deployment Model of GaussDB Distributed Instances?

  • Distributed (independent deployment)
    • This model is suitable for scenarios where there is a need to process a large amount of data, improve the storage capacity and concurrency of instances through scale-out, and the performance requirements cannot be met by deploying a distributed instance in combined deployment.
    • Each component is deployed on its own ECS, guaranteeing uninterrupted performance but at a higher cost. For example, in the default configuration (3 CNs, 3 replicas, and 3 shards), a total of 18 ECSs are required, including three CNs, nine DNs, three CMSs, and three GTMs.
  • Distributed (combined deployment)
    • This model is suitable for scenarios with large data volumes, potential future data volume growth, moderate performance requirements, and a need for a distributed database.
    • All components are deployed on the same ECS. For example, in a combined deployment with one primary node and two standby nodes, only three ECSs are required. In complex service scenarios, performance contention may arise as all components share the same ECS. Consequently, the overall performance of combined deployment is slightly lower than that of independent deployment with the same specifications.
Parent topic: About GaussDB