Thank you !!!
*** yes, I think you should use Redis caching, and I don't think you have to make it as complicated as pub/sub. Just update the cached values in Redis when they change in the DB
I guess this will be the first iteration of the implementation, which will be triggered once the list/meta_tables is requested only ... via a simple Redis wrapper with setMeta and getMeta subs, which will first serialize the hash ref of hash refs ( with Data::Dumper or Storable ) and set it to redis , than desirialize it and serve to clients ... when requested ...
*** Both Redis and the Perl Redis interface are very stable
Glad to hear that - the most important aspect, I forgot to ask even ...
*** For multi-process data sharing in general, see MCE and MCE::Shared ...
I guess multi-process sharing will not make sense architecturally-wise ... if one would like to use later one multiple application layer boxes ...
*** Hope this helps!
Yes, indeed. Many Thanks ! I will post a git commit-hash link in this discussion later on ... once implemented ...
In reply to Re^2: multiprocess run-time data structure sharing in Mojolicious web app ...
by YordanGeorgiev
in thread multiprocess run-time data structure sharing in Mojolicious web app ...
by YordanGeorgiev
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |