t;
Date: Wednesday, November 29, 2017 at 1:19 PM
To: MarkLogic Developer Discussion
mailto:general@developer.marklogic.com>>
Subject: Re: [MarkLogic Dev General] Multi-Database Architecture
Actually, it is the other way around. MarkLogic prefers multiple forests above
a single forest...
Don’t p
> Reply-To: MarkLogic Developer Discussion
> Date: Tuesday, November 28, 2017 at 10:59 AM
> To: MarkLogic Developer Discussion
> Subject: Re: [MarkLogic Dev General] Multi-Database Architecture
>
> Hi,
>
> The clients are different services in a larger micro-service landsc
Hubmer
mailto:andreas.hub...@ebcont.com>>
Reply-To: MarkLogic Developer Discussion
mailto:general@developer.marklogic.com>>
Date: Tuesday, November 28, 2017 at 10:59 AM
To: MarkLogic Developer Discussion
mailto:general@developer.marklogic.com>>
Subject: Re: [MarkLogic Dev General] Multi-D
obably think of many more yourself.
>
> Cheers,
> Geert
>
> From: on behalf of Andreas
> Hubmer
> Reply-To: MarkLogic Developer Discussion
> Date: Thursday, November 23, 2017 at 4:53 PM
> To: MarkLogic Developer Discussion
> Subject: [MarkLogic Dev General] Multi-Datab
rklogic.com>>
Date: Thursday, November 23, 2017 at 4:53 PM
To: MarkLogic Developer Discussion
mailto:general@developer.marklogic.com>>
Subject: [MarkLogic Dev General] Multi-Database Architecture
Hi,
I am planning the architecture of an application with dozens of individual
client
o: MarkLogic Developer Discussion
mailto:general@developer.marklogic.com>>
Date: Thursday, November 23, 2017 at 4:53 PM
To: MarkLogic Developer Discussion
mailto:general@developer.marklogic.com>>
Subject: [MarkLogic Dev General] Multi-Database Architecture
Hi,
I am planning the architectur
Hi,
I am planning the architecture of an application with dozens of individual
clients. I think of using either one database for all data or a separate
database per client.
The main pros and cons for me are efficient memory usage and the
possibility of individual backup&restore. I tend to prefer
