Difficult to say without know what the architecture exactly is... Sharing a database between app is not supposed to cause any issue since web2py allow you to have multiples connections strings, this is true in reading, but when you write in this database you may facing lock if multiples concurrent insert or update occurs depending of the backend used or in case of heavy usage condition.
Richard On Tue, Sep 22, 2015 at 1:04 PM, Alex Glaros <[email protected]> wrote: > Many government organizations will share my cloud-based app. > > Some app features, such as mass idea sharing, need a common table to make > it work. > > Other app features such as individual organization workflow do not require > a shared table as they are specific to each organization. A single, common, > centralized, shared table for workflow would work at first, but I wonder if > it would slow down after a while, and if it's architecturally effective to > give each organization a separate workflow table. Would that scale > correctly? > > thanks, > > Alex Glaros > > -- > Resources: > - http://web2py.com > - http://web2py.com/book (Documentation) > - http://github.com/web2py/web2py (Source code) > - https://code.google.com/p/web2py/issues/list (Report Issues) > --- > You received this message because you are subscribed to the Google Groups > "web2py-users" 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. > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" 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.
