This content has been marked as final. Show 3 replies
Really no suggestions from the experts here?
who says experts on your specific problem visit here?
In any case your real problem is that you just don't know enough. So at this point you really cannot be helped. Study more and the answer will become clear to you in time. Or perhaps you'll realize you are attempting to use the wrong tool for the job...
The more "static" case of a JEE architecture that gets deployed once and handles just one tenant is quite obvious to me, I think.
My difficulties came in with the necessity of more dynamism when handling more than one tenants and optimally NOT mixing up data of all the tenants in just one shared database (I mean ... even the case for handling 2+ tenants and storing all their data in just 1 database is quite obvious to me, at least theoretically at the moment).
So, in 1st place, my question targeted at getting some advice which way to go on ... or in other words ...
a brief sketch of the top-level component arrangement (top-level architecture) that is good practice for implementing an Online Website Builder web app in Java at the moment !?!
gimbal2 wrote:...I thought experienced users could provide me either this feasibility or non-feasibility information and, in the former case, a brief description of a workable arch in a few "top-level sentences" to get me in the right direction and shorten study time a bit. Maybe I was wrong.
[...] Study more and the answer will become clear to you in time. Or perhaps you'll realize you are attempting to use the wrong tool for the job...
Still hoping for some directional advice I rest with