Handling Redis failure
up vote
0
down vote
favorite
I have the following architecture:
Timeline data for users are added to the cache when they are posted.
If older data are requested but they can't be found in the cache, I go to the database.
This is all ok.
But I wonder how the problem should be fixed if Redis fails; in that case the strategy fails. New posts don't get written to the cache, so they cannot be retrieved when Redis gets up again either.
What is the usual way to handle this problem?
caching redis
add a comment |
up vote
0
down vote
favorite
I have the following architecture:
Timeline data for users are added to the cache when they are posted.
If older data are requested but they can't be found in the cache, I go to the database.
This is all ok.
But I wonder how the problem should be fixed if Redis fails; in that case the strategy fails. New posts don't get written to the cache, so they cannot be retrieved when Redis gets up again either.
What is the usual way to handle this problem?
caching redis
1
To mitigate component failures, you can deploy Redis in a highly-available fashion.
– Itamar Haber
Nov 21 at 18:18
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have the following architecture:
Timeline data for users are added to the cache when they are posted.
If older data are requested but they can't be found in the cache, I go to the database.
This is all ok.
But I wonder how the problem should be fixed if Redis fails; in that case the strategy fails. New posts don't get written to the cache, so they cannot be retrieved when Redis gets up again either.
What is the usual way to handle this problem?
caching redis
I have the following architecture:
Timeline data for users are added to the cache when they are posted.
If older data are requested but they can't be found in the cache, I go to the database.
This is all ok.
But I wonder how the problem should be fixed if Redis fails; in that case the strategy fails. New posts don't get written to the cache, so they cannot be retrieved when Redis gets up again either.
What is the usual way to handle this problem?
caching redis
caching redis
asked Nov 21 at 17:53
Trace
7,98853686
7,98853686
1
To mitigate component failures, you can deploy Redis in a highly-available fashion.
– Itamar Haber
Nov 21 at 18:18
add a comment |
1
To mitigate component failures, you can deploy Redis in a highly-available fashion.
– Itamar Haber
Nov 21 at 18:18
1
1
To mitigate component failures, you can deploy Redis in a highly-available fashion.
– Itamar Haber
Nov 21 at 18:18
To mitigate component failures, you can deploy Redis in a highly-available fashion.
– Itamar Haber
Nov 21 at 18:18
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53417952%2fhandling-redis-failure%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
To mitigate component failures, you can deploy Redis in a highly-available fashion.
– Itamar Haber
Nov 21 at 18:18