Eliminate Print Servers: go LANless?
-
@johnhooks said:
@scottalanmiller said:
A database per customer results in weird things too, like having to automate the creation of databases. Which of course you can do, and pretty easily, but it is a step above normal database code and a big weird. If you think about many applications, when they are installed they expect that you are going to have created a database manually for them and set up permissions.
But if you are going to automate database management from the application then the security between databases has to be removed so that the single application can manage them all. Which pretty much defeats the purpose. It's still a single app talking to a single RDBMS, just tons and tons of individual databases to query against.
Another good point. I was thinking of the recent switch to Epicor that we had. I don't think any of that was automatic. The time it took for them to set everything up and let us know seemed like it was all manual. I guess I was making broad assumptions.
I would assume so, even Wordpress and super simple things don't automate that process at this point.
-
And... you'd need a database to track the databases!
Actually, as I think about it, separating databases really just becomes semantics. As long as it is a single application, separating the databases adds overhead (mostly for the developers) but in reality, it is always still all one datastore. One way or another, the application has to behave essentially the same no matter which way you do it.
The one advantage to having them separate is that you can have different "versions" for different customers. But I'm not sure that that is a good thing.
