|more useful options|
performance with mysql / file-caching / hash reference on demandby derion (Acolyte)
|on May 01, 2021 at 22:36 UTC||Need Help??|
derion has asked for the wisdom of the Perl Monks concerning the following question:
I am looking for a good not "the" way to keep my website/webshop fast with growing complexity of data structure.
A lot of statements say it makes sense to keep the data in the database and build the pages on demand.
I tried to store the information in files e.g. as JSON but updating it and the performance did not really make me happy. Keep everything in one file or create one file per information group (e.g. price of the product, variants, properties). Both ways did not really make me happy.
Storing the data in the database as JSON seems to be an option but as my DB is still latin-1 I would prefer not to mix things where as far as I can see JSON should be stored as UTF-8.
I stumbled over freezing / thawing hashrefs and storing them in a DB. No statement I read about that was really emphatic but still it seems kind of elegant in my eyes.
My idea was to make one table with text or blob cols where one col is the price of an item, one is for the properties and so there could be several more.
I am uncertain because what I read seems to say I am going the wrong way. What I have experienced says the ways I have tried are not very good.
I would be very happy to get some opinions that could direct me to a good way to go on.
Thank you very much