[DOCU-2409] Create Database setup and sizing page (QnA) Created: 07/Mar/22  Updated: 14/Mar/22  Resolved: 14/Mar/22

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

Type: Task Priority: Neutral
Reporter: Martin Drápela Assignee: Martin Drápela
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

 Description   

Create a QnA includable content called Database sizing and setup,

 

Content: (polish) from the original slack post #pd (jordan):

Jordan  4 days ago

Hi guys, I have a client asking the following questions regarding the DB setup for magnolia. I looked through the docu but I'm not finding anything that answers these questions explicitly
Here are the questions being asked:
What volume of data does your application store?:
Approximately how many database tables are within the database (e.g., 100, 200, 300)?:
How many database instances or servers do you have?:
What are the database operating system(s)?:
What sort of data does this DB store?
Does Magnolia store structured and/or unstructured data?:
 
yan  4 days ago

What volume of data does your application store?:

Volume of data required to run Magnolia is negligible (below 10MB). The main driver of total volume is the content customer decides to store in Magnolia and number of versions of that content. It's safe to assume that reasonable operational size should be double the amount of data customer has now if versions of content are stored or less if running without versioning.

Approximately how many database tables are within the database (e.g., 100, 200, 300)?:

There's 4 tables and 2 indices created for every workspace. The total amount of workspases depends on modules customer decides to use and custom types created by customer (each type means one workspace). Default bundle comes with approx 20 workspaces, so around 80 tables.

How many database instances or servers do you have?:

This is fully configurable. Client can run all instances against same database instance and just use different table spaces or prefixes for tables used by different workspaces. However to improve disaster tolerance we recommend to run fully redundant setup with each Magnolia instance being backed by independent DB instance. In between combination is also possible (some instances sharing DB and some running their own).

What are the database operating system(s)?:

Client is free to choose from all databases officially supported by JackRabbit and from all OSes supported by those DBs. All major DBs are supported at the moment. We would recommend going with Postgres

What sort of data does this DB store?

This is configurable. By default DB would store only text based data up to the size of 1KB of text. The limit can be raised. It is also possible to configure datastore (binaries) to be stored in DB. While it increases load on DB, it will greatly simplify backup/restore strategy and thus as such is recommended setup. In that case all data would be in the database and there would be additional table in DB per workspace (ie 5 tables per content type instead of 4).

Does Magnolia store structured and/or unstructured data?:


Structured, however not directly open for manipulation at the DB level. Data are optimized for storage through hierarchical-to-relational data mapping to make it perform best at runtime as hierarchical data and best at storage time in relational DB storage.


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