Magnolia 5.6 reached end of life on June 25, 2020. This branch is no longer supported, see End-of-life policy.
Attachments
| Name | Size | Creator | Creation Date | Labels | Comment | ||
|---|---|---|---|---|---|---|---|
| PNG File data-strore-deployment-clustered.png | 64 kB | Julie Legendre | 2017-11-08T10:30:46+01 |
|
Data store deployment option 3: Clustered data store. All public instances run in a cluster. | ||
| Version 1 (current) | 64 kB | Julie Legendre | 2017-11-08T10:30:46+01 | Data store deployment option 3: Clustered data store. All public instances run in a cluster. | |||
| PNG File data-strore-deployment-central-database-server.png | 81 kB | Julie Legendre | 2017-11-08T10:30:44+01 |
|
Data store deployment option 2: Centralized database server. A centralized database server holds the copies of JCR repositories for each instance. But the instances run in separate virtual machines. This setup is performant but not disaster tolerant. | ||
| Version 1 (current) | 81 kB | Julie Legendre | 2017-11-08T10:30:44+01 | Data store deployment option 2: Centralized database server. A centralized database server holds the copies of JCR repositories for each instance. But the instances run in separate virtual machines. This setup is performant but not disaster tolerant. | |||
| PNG File data-strore-deployment-separate-instances.png | 48 kB | Julie Legendre | 2017-11-08T10:30:42+01 |
|
Data store deployment option 1: Completely separate instances. Each instance has a dedicated database and runs on different physical hardware. This setup is good for zero downtime. | ||
| Version 1 (current) | 48 kB | Julie Legendre | 2017-11-08T10:30:42+01 | Data store deployment option 1: Completely separate instances. Each instance has a dedicated database and runs on different physical hardware. This setup is good for zero downtime. |
Overview
Content Tools