Re: how to split backend storages of ZEO

I am trying 

How to serve multiple file storages from a single ZEO server (and reference 
them from a single cllient application with multiple nodes)

I want to store some blobs in database and application will keep deleting 
these blobs and then creating new blobs. Application can create/delete 100s 
of blobs per minute. I do not want to store these blobs in main database to 
avoid frequent packing. plus we want to store settings and records in 
separate storage. In case of database corruptions, this will let our 
customers start their system again with settings storage only.usually 
customers are OK if their records are gone but their workflow is live again.

on another side,
Will this design give a better write performance of DB ?  If yes, then In 
future I may require to store different type of objects in separate storage.

Sanjay



On Thursday, 18 August 2016 19:26:06 UTC+5:30, Jim Fulton wrote:
>
>
>
> On Thu, Aug 18, 2016 at 3:41 AM, Sanjay Rao <[email protected] 
> <javascript:>> wrote:
>
>> Hi,
>>
>> Is there a way to define two backend file storage with ZEO.
>>
>
> I don't know what you're asking. Are you asking:
>
> - How to reference two ZEO servers in a single client application?
>
> or
>
> - How to serve multiple file storages from a single ZEO server (and 
> reference them from a single client application)?
>
> or something else?
>
>  
>
>> I want to create separate files for different type of objects. A simple 
>> classification of objects could be
>> - Settings and setup related things in one data.fs
>> - All other records in a separate data.fs
>>
>
> Why do you want to do this?
>
> 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.