Proficient in NoSQL to see if there is any good solution to this situation? What should I do?

If you are proficient in NoSQL, what are the best solutions for this situation ?? The database of website A has A very simple table xx, field: id: Auto-incrementing key: value is the only character value: the value is any string. Website B needs to read data from Table xx in website A every day. My current practice is: whenever the website A operates on the xx table, it will synchronize to the mysql database in remote server C and be proficient in NoSQL to see if there is any good solution to this situation ??
The database of website A has A very simple table xx, field:
Id: Auto-increment
Key: The value is a unique character.
Value: The value is an arbitrary string.

Website B needs to read the xx table data in website A every day.


My current practice is:

When website A operates the xx table, it synchronizes the same operation to the mysql database in remote server C. In this way, website B reads data from remote server C every day for query and display. However, the performance of this method is still a problem. during the query, you need to connect to the mysql database in remote server C. Although Website B caches data locally after querying and obtaining data, but I still feel unsatisfied.


Recently I found that NoSQL should be more suitable for storing my xx table. so how can I perform better operations with NoSQL?


I also came up with a method:

When website A operates Table xx, every time A new record or modification record is inserted, A corresponding txt file is generated for each record under A directory, with the file name as key, the file content is value. In this way, each time Website B queries data, there is no txt file name under the Directory a of the curl website. If yes, the value is displayed. The disadvantage of this method is that A large number of small files are generated under A directory of website.

Or is there any good way to save the data in Table xx to a file? And then transfer it to website B? Then, perform operations such as local query on website B. The disadvantage is that every time the xx table on the website has an update operation, the file needs to be synchronized to Site B.

------ Solution --------------------
Memcache is not a good solution... or the redis
The best way to share data with several servers is to avoid massive data volumes. The boss said the memory is very expensive. Haha