| > 1. We have a web app that will be used by many, many people. We
| > would like
| > to host this app on a cluster of servers. The catch is, we want
| > everyone to
|
| Is it one company per box? Or multiple? If it's one company per box, then
| just use the same DNS name and point to the a di
> 1. We have a web app that will be used by many, many people. We
> would like
> to host this app on a cluster of servers. The catch is, we want
> everyone to
Is it one company per box? Or multiple? If it's one company per box, then
just use the same DNS name and point to the a different db on
I need some suggestions on several different topics here.
1. We have a web app that will be used by many, many people. We would like
to host this app on a cluster of servers. The catch is, we want everyone to
use the same copy of code for the app, but each person/company needs their
own databa
3 matches
Mail list logo