User475983607 posted
how can i handle large files by reading the data that i need and saving the changes only. so avoid reading and writing everything.
as ive seen an infinite of times by other posts:
I AM NOT LOOKING FOR BUFFERING/CASHING. IM LOOKING FOR SPEEDING UP ACCES TO THE FILE. SINCE THE LIFESPAN OF THE APP IS LESS THAN A SECOND. this is why the speed has to be found in the reading and writing, rather than buffering an instance of the file.
Your question infers that building something like this is common knowledge. The truth is it requires a fair amount of Computer Engineering and knowledge of the target platform. The common solution for us mere mortals is a making use of a database
(or distributed cache) as the folks that build these services handled the technical details.
This advice has been given freely to you over your many threads on the this subject.
If you are interested in learning the technical details, I suggest that you visit a support forum more inline with the subject. Or perhaps take a few CE classes.