Re: ZODB and mounting points

On Wed, Dec 20, 2017 at 7:13 AM, Héctor Velarde <[email protected]>
wrote:

> sorry for cross-posting but this seems to be a better place to ask for
> information.
>

I'm curious if you got an answer elsewhere. :)


>
> we have a customer that is used to create their Plone sites on the same
> Zope using multiple mounting points and I want to understand what are the
> advantages/disadvantages of this approach.
>
> unfortunately there’s not much information about this topic on the
> internet and the main article mentioning it is very vague:
>
> http://web.archive.org/web/20080611061803/http://plone.org/
> documentation/how-to/multiple-plone-sites-per-zope-instance-
> using-separate-data-fs-files-for-each-one
>
> is somebody here using this approach? is this considered a good practice?
> why?
>

I think "good practice" has to be evaluated in the context of requirements.

More broadly, on the topic of using multiple databases in an application,
there are a number of reasons why this might make sense for an application:

   - Manually sharding

   This might be done to provide greater database performance, although I
   would only do this if I was transactions were unlikely to modify multiple
   databases, in which case, a microservice architecture might provide a
   better approach.

   - Requirements for separate database-management policy

   For example, you might separate content from index data, packing the
   later more frequently. Or you might want to keep separate customer data in
   separate databases.

The potential  benefits of using multiple databases has be weighed against
significant increase in complexity, especially in the presence of
non-trivial cross-database references.

Jim

-- 
Jim Fulton
http://jimfulton.info

-- 
You received this message because you are subscribed to the Google Groups "zodb" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.