How to use Redis Bloom filter

This article introduces the knowledge of "how to use Redis Bloom filter". In the operation of practical cases, many people will encounter such a dilemma, so let the editor lead you to learn how to deal with these situations. I hope you can read it carefully and be able to achieve something!

When it says that the user id is not in the container, it is definitely not. When it says that the user id is in the container, there is a 99% chance that it is correct, and there is a 1% chance that it has made a misjudgment. However, in this case, this miscalculation will not cause a problem, and the price of misjudgment is only cache penetration, which means that 1% of new users are directly penetrated into database queries without the protection of Bloom filters. the remaining 99% of new users can be effectively blocked by Bloom filters to avoid cache penetration.

Def get_user_state (user_id): exists = bloomfilter.is_user_exists (user_id) if not exists: return {} return get_user_state0 (user_id) def save_user_state (user_id, state): bloomfilter.set_user_exists (user_id) save_user_state0 (user_id, state) copy code

The principle of Bloom filter has a good analogy, that is, on a snow-covered ground in winter, if you walk through it, you will leave your footprints. If there are your footprints on the ground, then there is a good chance that you have been to this place, but not necessarily, maybe other people's shoes are exactly the same as what you are wearing. But if there are no footprints on the ground, you can be 100% sure that you have never been to this place.

This is the end of "how to use Redis Bloom filter". Thank you for reading. If you want to know more about the industry, you can follow the website, the editor will output more high-quality practical articles for you!