The company is currently a small company and is developing a social APP that involves the APIS required by the APP (node. js), PC-end user center website (php), General Management Center (java), currently using mysql database, everyone uses redis cache on different platforms, but the problem is that, modified through API... the company is currently a small company and is developing a social APP that involves the APIS required by the APP (node. js), PC-end user center website (php), General Management Center (java), currently using mysql database, everyone uses redis cache on different platforms, but the problem is that, when the database and A cache are modified through APIS, the PC-side website cache is unknown and cannot be updated in time. How to Design the cache is more scientific?
You are welcome to recommend front-end development engineers, architects, and DBAs for yourself :)
Reply content:
The company is currently a small company and is developing a social APP that involves the APIS required by the APP (node. js), PC-end user center website (php), General Management Center (java), currently using mysql database, everyone uses redis cache on different platforms, but the problem is that, when the database and A cache are modified through APIS, the PC-side website cache is unknown and cannot be updated in time. How to Design the cache is more scientific?
You are welcome to recommend front-end development engineers, architects, and DBAs for yourself :)
In our previous systems, cache was centrally planned by the same person, and then maintained by the principle of WHO updates data and who maintains the cache.
Based on the business, you can plan cache content in a unified manner and save only one copy of the cache. When you access the same copy, you can ensure that all the obtained content is up-to-date. This technology is not difficult, but it requires strong high-level execution.