Solutions for “Maintenance Mode”
Given a web application running across 10+ servers, what techniques have you put in place for doing things like altering the state of your website so that you can implement certain features.
Basic memcached question
I have been reading up on distributed hashing. I learnt that consistent hashing is used for distributing the keys among cache machines. I also learnt that, a key is duplicated on mutiple caches to handle failure of cache hosts. But what I have come across on memcached doesn’t seem to be in alignment with all this. I read that all cache nodes are independent of each other and that if a cache goes down, requests go to DB. Theres no mention of cache miss on a host resulting in the host directing the request to another host which could either be holding the key or is nearer to the key.
Shared Cache – Invalidation Best Practice
I’d like to know what would be a better approach to invalidate/update cache objects.
Architecture change from using disk to RAM to read and write key/value pairs coming over a network
A WebApp writes a stream of data coming over a network to disk as key/value pair and then reads & send it over network again after few milliseconds in 99% of case. In 1% of cases write/read can be few hours to days apart (really don’t know).
The memcache clears itself
The memcache clears itself.
I installed memcache, after installation (or reboot) the memcache memory accumulates almost 2GB of records, then it suddenly starts clearing itself. and after that, only 200 MB of records are collected. and also, the volume of data in the memcache constantly decreases and increases.
Why is the data not kept stable in the memcache memory? The memory limit is 6 GB; there is a lot of RAM on the server.
PHP memcached addserver don’t return False when server is down
PHP version: 7.2.6
design for buffering or queuing data streams to replace database
We have a system (ms stack, .net, sql) that receives data from thousands of remote devices (several independent readings/min). We currently save all the data to a db as it arrives and a second service reads and processes the data – using the database to ‘buffer’ the input.