> Generally, you don't need a separate DB for each subdomain. One big DB > is usually better.
It's a high volume app, that's written as a standalone service. Extending it as a hosted solution and keeping updates nice is a big part of what the project is about.
>> Generally, you don't need a separate DB for each subdomain. One big DB >> is usually better.
> It's a high volume app, that's written as a standalone service. > Extending it as a hosted solution and keeping updates nice is a big > part of what the project is about.
And all of that would be easier with one big DB, at least as far as you've described.
> > It's a high volume app, that's written as a standalone service. > > Extending it as a hosted solution and keeping updates nice is a big > > part of what the project is about.
> And all of that would be easier with one big DB, at least as far as > you've described.
You are right, it would definitely be easier if this App was written with a hosted version in mind. Unfortunately it isn't.
Still, the volume of traffic and DB size of the app means that if someone grows bigger we want to be able to quickly move it to something dedicated.
> > > It's a high volume app, that's written as a standalone service. > > > Extending it as a hosted solution and keeping updates nice is a big > > > part of what the project is about.
> > And all of that would be easier with one big DB, at least as far as > > you've described.
> You are right, it would definitely be easier if this App was written > with a hosted version in mind. Unfortunately it isn't.
> Still, the volume of traffic and DB size of the app means that if > someone grows bigger we want to be able to quickly move it to > something dedicated.
