took a look at WPMU and they really are duplicating the tables. Is there any cons I should think of if my web app has 50-100 tables?
looks like number of tables would grow real quick, is that a problem? On Tue, Dec 30, 2008 at 1:23 PM, MartinB <[email protected]> wrote: > > So you're saying that if my app for 1 business has 5 tables, if I have > 10 customers, my db would have 50 tables? or you're saying to add an > extra table that hold the customer info and add a foreign key to every > other table? > > I will take a look at WPMU as well. > > Thanks > > On Dec 23, 12:32 pm, sheatsb <[email protected]> wrote: > > I'm assuming that this app would have different subdomains, such as: > > > > biz1.myapp.com > > biz2.myapp.com > > biz3.myapp.com > > > > If you code your app the right way, the mutli-tenant side is somewhat > > easy to manage. WordPress does it with wordpress.com and the open > > source version of it, WPMU. The DB will get bigger, but you can store > > the prefs and other details in the same db. Creating a new app w/its > > own db would be creating a maintenance and file nightmare. > > > > How it would work: > > > > 1 - build your app with multi-tenant code > > 2 - when new users set-up, add db tables to your db for the new > > customer (storing prefs and plugin options here will save you a lot of > > time) > > 3 - as everything grows, scalr will scale out your db, but as you run > > out of space (if your app becomes that popular), you're probably going > > to have to code for more than one db. > > > > So it's not so difficult, as long as you code it well. Scalr has been > > remarkably good about keeping everything simple. > > > > On Dec 23, 11:34 am, MartinB <[email protected]> wrote: > > > > > Hi, > > > > > I considering offering hosted version of my web app. So I'm thinking > > > of modifying the code to make it multi-tenant (a single web app that > > > manage customers from within the app). Doing so would require a lot of > > > time to make change to the code, but it would certainly be easier to > > > scale using scalr since it would be considered a single web app. > > > > > Also, making an app multi-tenant will also prevent (or at least make > > > it a lot more difficult) to customize it for every customers. So I'm > > > also considering that for each customer signup, I would setup a > > > different app with its own db. > > > > > That way, if a customer wants to install specific plugin, it's easier > > > that way since it won't affect others. > > > > > So my question is would it be possible to scale this using scalr? How > > > would it work? Every time a customer signs up, I would have a script > > > update apache config to add a new customer.mydomain.com? How would > > > that automatically update scalr settings so customer.mydomain.com is > > > managed by scalr in a way that a single farm could manage many > > > customers? Is this possible at all with scalr or it's not meant for > > > that kind of situation? > > > > > Thanks > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/scalr-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
