Don't ask to ask, just ask | |
PerlMonks |
Re^3: OT: Scalable web application architectureby dokkeldepper (Friar) |
on Dec 07, 2005 at 13:17 UTC ( [id://514826]=note: print w/replies, xml ) | Need Help?? |
Your caching via database table has a serious problem: It is simultaneously queried via select(s), update(s) and refreshed via 'insert into'. These operations have very different indexing needs to perform well, these are practically impossible to meet simultanerously. Not to speak of the locking issues. A better architectural idea would be to cache some data in a perl-Structure, update it there and push it back into the database after processing is done. This solution requires some amount of bookkeeping, in particular if it is a distributed system. If it is havily distributed (several geographical locations) think about replication. Please check the indexing of the underlying database architecture. Some millions of lines are easily processed if the indexing is right. How about data architecture? Have you separated the static data from the dynamic data? The property, package and room data seems to be static, the reservation data is dynamic, separate these into different tables.
In Section
Seekers of Perl Wisdom
|
|