how many gigabytes of data are we talking about and how many queries per sec (or,even better, the mean response time of the database) ? What's your estimated growth ? Sure, if you are around 500GB, +300queries/sec and +10k users, it'd be time to figure out a scale-out approach (in which a "logical" separation makes sense as it's the easiest one) for the backend. Just don't think too hard if you are below the previous specs. VS these days are cheap.
On Friday, January 15, 2016 at 6:26:53 PM UTC+1, Pierre wrote: > > > I am afraid my app might break as its database size grows (db bottlenecks > , any hardware/software overload). To prevent that I am thinking about > dividing it by country : one independent app +database for every country. > Do you think this is a good idea ? > > > in other words centralization vs distribution ? > > > -- 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 web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
