多租戶系統的建立目標
A multitenant environment enables the central management of multiple PDBs in a single installation. By using a multitenant environment, you can accomplish the following goals:
· Cost reduction------降低成本
By consolidating合併、鞏固 hardware and sharing database memory and files, you reduce costs for hardware, storage, availability, and labor工作量、勞動. For example, 100 PDBs on a single server share one database instance and one set of database files, thereby requiring less hardware and fewer personnel.
· Easier and more rapid movement of data and code---簡單會計的資料、程式碼移動
By design, you can plug a PDB into a CDB, unplug the PDB from the CDB, and then plug this PDB into a different CDB. Therefore, you can easily move an application's database back end from one server to another.
· Easier management and monitoring of the physical database簡化管理、監控物理DB
The CDB administrator can attend to one physical database (one set of files and one set of database instances) rather than split attention among dozens or hundreds of non-CDBs. Backup strategies and disaster recovery are simplified.
· Separation of data and code-----資料和程式碼的分離
Although consolidated into a single physical CDB, PDBs mimic the behavior of traditional non-CDBs. For example, if a user error causes data loss, then a PDB administrator can use point-in-time recovery to retrieve the lost data without affecting other PDBs.
· Ease of performance tuning-----簡單的效能診斷
It is easier to collect performance metrics for a CDB than for multiple non-CDBs. It is easier to size one SGA than several SGAs.
· Support for Oracle Database Resource Manager-----支援oracle資源管理
In a CDB, one concern is contention for system resources among the PDBs running on the same server. Another concern is limiting resource usage for more consistent, predictable performance. To address such resource contention, usage, and monitoring issues, you can use Oracle Database Resource Manager (see ).
· Fewer patches and upgrades---------減少了打補丁與升級操作
It is easier to apply a patch to one CDB than to multiple non-CDBs and to upgrade one CDB than to upgrade several non-CDBs.
A multitenant environment is especially useful when you have many non-CDBs deployed on different hardware in multiple Oracle Database installations. These non-CDBs might use only a fraction of the hardware resources dedicated to them, and each one might not require a full-time database administrator to manage it.
By combining these non-CDBs into a CDB, you can make better use of your hardware resources and database administrator resources. In addition, you can move a PDB from one CDB to another without requiring changes to the applications that depend on the PDB.
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/28612416/viewspace-1368695/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- 多租戶商城系統解說
- 多租戶系統的核心概念模型模型
- 多租戶系統的應用架構應用架構
- 多租戶
- Part II 建立和配置多租戶環境
- SaaS架構:多租戶系統架構設計架構
- MaxCompute多租戶資料安全體系
- 2 多租戶體系結構概述
- Part III PDB建立概述-Oracle多租戶管理員指南Oracle
- 1.2. 多租戶體系結構的優點
- 大資料體系下的多租戶管理方案大資料
- java B2B2C 多租戶電子商城系統Java
- 吊打面試官!全網最全多租戶系統設計方案面試
- B2B2C多租戶商城系統解決方案
- 多租戶解析與Demo
- 3.3.2 多租戶環境的工具
- 1.1. 關於多租戶體系結構
- Part II 建立和配置CDB-Oracle多租戶管理員指南Oracle
- java B2B2C Springboot多租戶電子商城系統JavaSpring Boot
- 新零售SaaS架構:多租戶系統架構設計架構
- Part II 配置和管理多租戶環境概述-Oracle多租戶管理員指南Oracle
- 3.3.1 多租戶環境的任務
- 如何理解多租戶架構?架構
- oracle 12c 多租戶體系結構概念Oracle
- 基於 SQL 解析的 JPA 多租戶方案SQL
- SaaS多租戶的3種隔離模式模式
- 2. Overview of the Multitenant Architecture(多租戶體系結構概述)ViewNaN
- Oracle 20C 多租戶_體系結構介紹Oracle
- 圖解:什麼是多租戶?圖解
- java B2B2C 多租戶電子商城系統-Spring Cloud ZipkinJavaSpringCloud
- java B2B2C springmvc mybatis多租戶電子商城系統--Zuul的高可用JavaSpringMVCMyBatisZuul
- 1.2.3. 多租戶管理帶來的好處
- 3.2 多租戶環境的先決條件
- 3 配置和管理多租戶環境的概述
- java B2B2C springmvc mybatis多租戶電子商城系統-gateway 限流JavaSpringMVCMyBatisGateway
- java B2B2C 多租戶電子商城系統-spring-cloud-configJavaSpringCloud
- java B2B2C Springboot多租戶電子商城系統-Consul 介紹JavaSpring Boot
- java B2B2C Springcloud多租戶電子商城系統-Spring Cloud SleuthJavaSpringGCCloud
- Oracle多租戶管理員指南-體系結構介紹01Oracle