Page tree

Magnolia 5.7 reached extended end of life on May 31, 2022. Support for this branch is limited, see End-of-life policy. Please note that to cover the extra maintenance effort, this EEoL period is a paid extension in the life of the branch. Customers who opt for the extended maintenance will need a new license key to run future versions of Magnolia 5.7. If you have any questions or to subscribe to the extended maintenance, please get in touch with your local contact at Magnolia.

This page compares different ways to store data between Magnolia instances. Each option has its pros and cons.

Option 1: Completely separate instances

Each instance has a dedicated database and runs on different physical hardware. This setup is good for zero downtime.

(plus) Tolerant, highly available, completely redundant
(minus) Duplication of data and cost of resources to keep them

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.

(plus) Save money on database licenses and maintenance
(plus) Retain separate copies of data
(minus) Database is a single point of failure (unless it is clustered)
(minus) Need to maintain more hardware or VMs

Option 3: Clustered data store

All public instances run in a cluster.

(plus) Low cost
(plus) Faster publishing
(plus) Sharing of user-generated content
(minus) Only one copy of data
(minus) If the cluster goes down you lose all public data

  • No labels