Actual data store and cache should be synchronized using the third approach you've already described in your question.
As you add data to your definitive store (i.e. your SQL database), you need to enqueue this data to some service bus or message queue, and let some asynchronous service do the whole synchronization using some kind of background process.
You don't want get into this cases (when not using a service bus and asynchronous service):
- Make your requests or processes slower because the user needs to wait until the data is both stored in your database and cache.
- Have the risk of a fail during the caching process and not being able to have a retry policy (which is usually a built-in feature in a service bus or some message queues). Also, this failure can end up in a partial or complete cache corruption and you won't be able to automatically and easily schedule some task to fix this situation.
BTW, you won't be always on this case (if a key isn't expired it means that it shouldn't be overwritten). It might depend on your actual domain.
https://stackoverflow.com/questions/36302972/how-to-update-redis-after-updating-database
https://redis.io/commands/sdiff
https://developers.google.com/web/tools/chrome-devtools/network/reference#timing-explanation
https://medium.com/@akalongman/phpredis-vs-predis-comparison-on-real-production-data-a819b48cbadb
Some relational shit may be useful:
https://github.com/akalongman/laravel-lodash
Install phpredis on ELB, manual always seem risky ?
http://qpleple.com/install-phpredis-on-amazon-beanstalk/
gcc missing
Redhat, CentOS:
yum groupinstall "Development Tools"
https://webstoked.com/install-phpredis-laravel-ubuntu/
Must watch ?
Oh, Laravel have build in throttle limit, it's cool ~
app/Http/Kernel.php
https://redis.io/topics/rediscli
https://stackoverflow.com/questions/49299958/how-would-redis-get-to-know-if-it-has-to-return-cached-data-or-fresh-data-from-d
Oh, too much
https://serverfault.com/questions/606185/how-does-vm-overcommit-memory-work
But it seem my app use few GB of memory (per 16GB !) but almost all CPU (2 vCPU ?)
So AWS c5.large seem better than r4.large.
Show hits / mis statatus:
redis-cli: info stats
Careful with quote ie.
Redis::get("user:{$userId}.reviewedshop.all");
vs
Redis::get('user:{$userId}.reviewedshop.all');
http://qpleple.com/install-phpredis-on-amazon-beanstalk/
Script install phpredis on AWS beanstalk
As you add data to your definitive store (i.e. your SQL database), you need to enqueue this data to some service bus or message queue, and let some asynchronous service do the whole synchronization using some kind of background process.
You don't want get into this cases (when not using a service bus and asynchronous service):
- Make your requests or processes slower because the user needs to wait until the data is both stored in your database and cache.
- Have the risk of a fail during the caching process and not being able to have a retry policy (which is usually a built-in feature in a service bus or some message queues). Also, this failure can end up in a partial or complete cache corruption and you won't be able to automatically and easily schedule some task to fix this situation.
BTW, you won't be always on this case (if a key isn't expired it means that it shouldn't be overwritten). It might depend on your actual domain.
https://stackoverflow.com/questions/36302972/how-to-update-redis-after-updating-database
https://redis.io/commands/sdiff
https://developers.google.com/web/tools/chrome-devtools/network/reference#timing-explanation
https://medium.com/@akalongman/phpredis-vs-predis-comparison-on-real-production-data-a819b48cbadb
Some relational shit may be useful:
https://github.com/akalongman/laravel-lodash
Install phpredis on ELB, manual always seem risky ?
http://qpleple.com/install-phpredis-on-amazon-beanstalk/
gcc missing
Redhat, CentOS:
yum groupinstall "Development Tools"
https://webstoked.com/install-phpredis-laravel-ubuntu/
Must watch ?
Oh, Laravel have build in throttle limit, it's cool ~
app/Http/Kernel.php
https://redis.io/topics/rediscli
https://stackoverflow.com/questions/49299958/how-would-redis-get-to-know-if-it-has-to-return-cached-data-or-fresh-data-from-d
Oh, too much
https://serverfault.com/questions/606185/how-does-vm-overcommit-memory-work
But it seem my app use few GB of memory (per 16GB !) but almost all CPU (2 vCPU ?)
So AWS c5.large seem better than r4.large.
Show hits / mis statatus:
redis-cli: info stats
Careful with quote ie.
Redis::get("user:{$userId}.reviewedshop.all");
vs
Redis::get('user:{$userId}.reviewedshop.all');
http://qpleple.com/install-phpredis-on-amazon-beanstalk/
Script install phpredis on AWS beanstalk
# these commands run before the application and web server are
# set up and the application version file is extracted.
commands:
01_redis_install:
# run this command from /tmp directory
cwd: /tmp
# don't run the command if phpredis is already installed (file /etc/php.d/redis.ini exists)
test: '[ ! -f /etc/php.d/redis.ini ] && echo "redis not installed"'
# executed only if test command succeeds
command: |
wget https://github.com/nicolasff/phpredis/zipball/master -O phpredis.zip \
&& unzip -o phpredis.zip \
&& cd nicolasff-phpredis-* \
&& phpize \
&& ./configure \
&& make \
&& make install \
&& echo extension=redis.so > /etc/php.d/redis.ini
Comments
Post a Comment