Application Structure

Yet another factor that I am not completely decided on is application structure. For example, should the data for ALL clients be kept in 1 db or a separate db for each? If kept in 1 db, sould the data be amalgamated in 1 set of tables, or should there be a set of tables for each client?

These are questions to which I don't think have "right" or "wrong" answers, but, just different consequences. Separate db's allows far greater room for individual clients to tailor their application but poses a problem for universal authentication.

Structure also covers things like OOP (use of classes), use of AJAX, ways to authenticate and so on. We will get to these areas later on but, for now, just try to think of all areas within Application Structure.

Again I think more input is needed here before a final decision can be made.

-- Just a thought that is the db's were separate, should a client want bespoke development on their data, it would be far easier to do, even if they contracted their own developer to do it.