[DOCU-1490] Update / enhance "Clustering" page Created: 25/Apr/18  Updated: 29/Jun/18  Resolved: 14/May/18

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Christoph Meier Assignee: Christoph Meier
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Sprint: Docu Sprint 49, Docu Sprint 50, Docu Sprint 51
Story Points: 0.5

 Description   

Jan recently was providing some good points concerning clustering - which should go into docs.
Since I was either too lazy or too busy - we have a ticket now.

re cluster:

  • it is still possible and supported to use cluster w/ magnolia cms
  • you should consider cluster only if:
    • you are in full control of the VMs on which cluster is running
    • your public instances are not treated as "disposable" with automatic up/down scaling based on load or
    • your publics have DB (cluster) running on separate VM that is not disposable
    • amount of writes is not too high (each write generates record in Journal table that is used to synchronize all cluster nodes thus generates additional chatter and load on each node (also due to sync of index))
    • you do not update Magnolia too frequently or do not require HA (when updating clusters, all cluster nodes except one need to be shutdown, and restarted w/ new libs after the first node was updated successfully)
  • when above conditions are not met, it is in all likelihood better to avoid using cluster and distribute data by other means (e.g. REST service to which data are written directly from client or using Magnolia Public instances as proxy writing to such externalized service and being accessible from/via all instances)

(from hipchat, Connected Services)


Generated at Mon Feb 12 01:18:34 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.