If the whole database is on a single machine, I'm not sure separate tables would help -- ultimately, a single server still has to handle all the queries. Instead, if you need to handle heavier loads, it might help to scale out to multiple servers. In that case, you could keep the workflow data for different organizations on different servers. Rather than doing this manually via separate tables (or databases) per organization, you could instead employ a more automated sharding solution (e.g., https://www.citusdata.com/citus-products/pg-shard/pg-shard-quick-start-guide).
However, before dealing with the complexity of sharding, you might start by setting up a master-slave <http://web2py.com/books/default/chapter/29/13/deployment-recipes#Using-replicated-databases> architecture with a single master, and just bump up the specs of the server hosting the master (where all the writes are happening). Depending on your traffic, you might find you never need to go beyond that stage. Anthony On Tuesday, September 22, 2015 at 1:04:13 PM UTC-4, Alex Glaros 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.
