architecture - Using Memcache for Centralization of Distributed Cache Against DB -
I'm new to remembering and thinking whether the following ideas work or exist with successful cases or just Going to the bin? Save me and any guidance is highly appreciated. It goes here ...
Currently 1 MySQL DB is using memmache using additional memory to feed the already hungry webserver, which works in the frontend. Now we are going to start a new DB and webserver again and have not forgotten a son hungry to eat, we are considering alternate ways to do mashchach so that more DB and webserver should be connected in the future quickly. Could:
- Introduce a standalone server that is dedicated to running a mammesk and it is a lot of stuff, with lots of RAM and hard disk apps < Li> Get all DB examples to feed the luggage memory server
- Monitor memory usage from time to time to create scaling in the future by launching more cluster memcache to load.
- Cash strategy and content can be used again in more than one webserver, who have the same style or data cache.
If this design works, what kind of fallback or precautions have already been made? That is because I can not repeat the mistakes and learn from others.
Thanks
There is one thing to be careful about this design :
What happens when the memcache server restarts (or failed) then you loose all your cache, the best case is that your site slows down during the rebuilding of the cache, the worst The situation is that your site does not have to rebuild the cache.
Comments
Post a Comment