DATA COMMUNICATION BETWEEN SERVER AND AN APP..

1. Write all data into files,
2. Make the files as zip,
3. Send the zip to server,
4. Server will unzip the zip file,
5. Read all the data line by line from the files and update the data.

** TRUST ME, THIS IS A PRODUCTION APP I HAVE SEEN FROM A CLIENT **

Why not? This is the way I import my Data at the moment.

Making 1.2 million post request is not really a alternative.

And the size of the data I send from one server to the other is reduced by 50 %

@JackToolsNet Come on man, For ur use case it may ok.. Is it ok If whatsapp like app uses this way of communication?? For each and every msg create one file, write data bla bla bla........... 🙄🙄

@balazee2

I understand. We almost had that disaster scenario play out here over a less than 1K xml payload. The 'powers that be' decided to bike-shed a simple xml request/response service by making the xml smaller by zipping/unzipping the data.

They justified the effort by the typical nonsense of "If we save 10 bytes of data on each request, in 10 years we'll save ..... and saving of over $100K". No one ever figured out where they got that money from, but looked good in the PowerPoint graph.

6 months later (longer story behind this) they were very proud of the data size savings, but when the network admins and DBAs analyzed the transactions (thank you AppDynamics) the 'savings' actually cost double because of the time it took to zip up the data (on the client side) and unzip (server side).

Architects still got their bonus.

@balazee2 exactly. The use case is the important thing.

I also have my rest APIs running.

Trying to find the best solution is the hardest part.

By the way I tried it with 1.2 million post request too 😁

It takes four hours. With zip files it takes 35 minutes.

@JackToolsNet yes, i should have mentioned the USE CASE. Even for small data like username, pw they were using this architecture, LOL

@balazee2 Yes that is crazy 😂

you forgot to say that data files are in excel 97 format.