Highly interactive web apps- would there must be more than one database? One for personalized content, one for other functions and/or data that might rely on a back end? Can anyone give me an idea.
I’m assuming you mean tables?
When I was much a newbie I used to have “one big table with everything” and then have PHP do all the heavy lifting. So the “must” is debatable. However, although this “worked” I soon realized it was not the best approach and that having better database architecture, table schemas, and query syntax, yielded benefits in spades.
It requires a larger investment up front but IMHO the effort you put into determining what data you need and what you will be doing with it will pay for itself in short order.
This will depend on what you mean by “highly interactive web app”.
This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.