Architecture Issue for handling large data from MySql Server

ZewpeWSwero

New Member
I have 5 tables with millions of rows. Question is I need to create a menu and even extend more maybe in the future. The select Queries to this tables is the heart of my Website. Any one visiting my site would amount to a dozen of select queries to the server. What would be the best architecture design that could be implemented in this case?[*]Using indexing and caching.[*]Generating an XML or JSON which can be used by all the users without the need to query the db each time. [XML or JSON could be generated via a cron job, My rows wont change in every 5 minutes].Or is there any other good solution to this? Even critiquing my ways i mentioned above is a valid answer.PS: I would be happy not to invest in more server power if the solution could lie in a better Software Architecture.
 
Back
Top